Why is 405 Method Not Allowed always returned?

[binarykitchen]

This on POST requests.

> User-Agent: curl/7.43.0
> Accept: */*
> Content-Length: 167
> Content-Type: application/x-www-form-urlencoded
> 
* upload completely sent off: 167 out of 167 bytes
< HTTP/1.1 405 Method Not Allowed
< Allow: GET, HEAD, OPTIONS
< Content-Length: 0
< Date: Sun, 13 Mar 2016 02:46:59 GMT
< Connection: keep-alive

It is this code for reproduction:
https://github.com/binarykitchen/videomail-client/blob/master/Gulpfile.js#L104

[binarykitchen]

Ah, I found the culprit. If uncomment the root option, then it works, no 405. Weird. Probably the connect.directory middleware is messing here with something else

[binarykitchen]

Hmmm, serve-index causes this. See line https://github.com/expressjs/serve-index/blob/master/index.js#L102 ... uhhhh :(

[binarykitchen]

a solution would be to rearrange the order. to run the custom middleware first before serve-index

[binarykitchen]

@justinmchase ping

[binarykitchen]

I think this commit broke it
1352e3d

Order of middleware is crucial. Please restore.

[justinmchase]

I'm swamped right now but took a look at it and didn't see any obvious reason why the order of the middleware would be changed. Can you send a PR, or at least help me narrow down where the issue is happening? If I generally knew a fix I could probably crank it out in hours, sorry for delay.

[binarykitchen]

@justinmchase here you go, it is very simple #171

[justinmchase]

Fixed in v3.1.1

[binarykitchen]

great, the error is gone now, all works fine like before. thanks for quick reaction

[binarykitchen]

ps: @justinmchase can you please look at #140?