NV/chrome-devtools-autosave — Issue #15: POST http://127.0.0.1:9104/save 500 (Internal Server Error)
Author: spencercarnage
Created: 2012-01-10 03:59:23+00:00
State: open

I'm getting the following error in the background.html console:

```javascript
POST http://127.0.0.1:9104/save 500 (Internal Server Error)
onRequest background.html:84
chrome.Event.dispatch extensions/event.js:183
chromeHidden.Port.dispatch OnConnect.connectEventextensions/miscellaneous_bindings.js:99
chrome.Event.dispatch extensions/event.js:183
chromeHidden.Port.dispatchOnMessage extensions/miscellaneous_bindings.js:164
```

I'm also seeing this chrome UI popup:

> URL
> (http://localhost:8000/file/path/styles.css?092011) doesn't match RegExp /^file:\/\/[^/]*\//

Here are my options settings:

> Resources: http://localhost:8000/
> Post to: http://127.0.0.1:9104/save

routes.js:

```javascript
export.routes = [{
from: /http:\/\/localhost:8000\//,
to: '/Users/spencer/Documents/webapp/path/to/html'
}];
```

Does the `to` key of the `routes` from routes.js need to point to the exact folder that my html file is in? I have a base root that holds a lot of different python files with my html files scattered all over the place.

Also, I'm seeing a slight discrepancy from the link on [how to use localhost] (https://github.com/NV/chrome-devtools-autosave/issues/7#issuecomment-3182946) and this [open issue] (https://github.com/NV/chrome-devtools-autosave/issues/14#issuecomment-3422199) in how you input the `Resource` in the options and the `from` key of `routes` in routes.js ( `http://localhost` vs `^http://my.domain.name/` with the caret character before http portion of the url)

I know one uses locahost vs a real web host but I imagine they would be the same.