search

drewzboto / grunt-connect-proxy

Grunt Connect support for proxying API calls during development
MIT License
424 stars 122 forks source link

Proxy error: HPE_INVALID_STATUS #113

Open danielcrisp opened 9 years ago

danielcrisp commented 9 years ago

I use grunt to start a local express server when I'm developing front end templates. Typically I'll be developing the templates and also the mock API endpoints I require for my web app.

My web app is started on port 9000 and my API server is on port 9001. The proxy allows me to access the API through port 9000 when I need to support browsers that can't use CORS.

I have just set up the marvellous Flow.js and implemented this example within my API server: https://github.com/flowjs/flow.js/tree/master/samples/Node.js

Unfortunately I am seeing the Proxy error: HPE_INVALID_STATUS error in Terminal when I try to upload a file.

If I disable grunt-connect-proxy and access the endpoint on port 9001 everything works great.

So although I don't think this is a bug with grunt-connect-proxy perhaps you could point me in the right direction as to what it means and how I might fix it!

haugthom commented 8 years ago

+1

jeroenvollenbrock commented 8 years ago

I'm replying to this topic because of it high search-rank when you search for this error. This error may occur when you're passing an invalid status code with the HTTP response from within nodeJS without checking for a valid status code, for instance an object instead of a number (I've seen a lot of HTTP/1.1 [Object object] responses pass by when i was helping someone to debug this behaviour)