Lemme have a look at lunch, see if anything has changed
I think I know why this is happening. Interfake accepts requests wildcard for method and path, so the OPTIONS request that chrome is probably making beforehand is being returned as the default, which is GET. Someone opened an issue relating to OPTIONS not being supported, and has offered to fix it, which should also solve this problem :)
Because OPTIONS requests actually don't seem to work at all, which now makes sense
@basicallydan Hello, I've been having trouble getting serveStatic to work. I basically copy and pasted the example code in, but I'm always getting a 404 response when I visit localhost:3000/static/index.html . The html file is in the same folder as my interfake code. Everything is working when I use the interfake.get().body() type examples but the serveStatic doesn't work for me. Any thoughts on why this would not be working? Thanks for any help you can provide.
@ddperdue I had a similar issue when I was trying to mix together serveStatic and other mappings at the same time. The solution I found was to separate out the first part of the URL to make sure there was no overlap between the static mappings and the non-static, otherwise interfake was trying to find the static mapping in the normal routes.
// Have to provide a path so it doesn't clash with the static serving.
var interfake = new Interfake({path: '/api'});
interfake.serveStatic('/static', './');
Was thinking of using this as a simple way to make some assertions against the response.
@jdenly, having problems with servestatic for a while
Been meaning to fix but have been on holiday, I was hoping to fix it today :)
Sorry about the delay
I'll let you know how I get on
Give it a go
Update to 1.14.0
Use .echo, it'll work.
or echo : true in the response object