New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

505 HTTP Version Not Supported #768

Closed
aoeking opened this Issue Dec 1, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@aoeking

aoeking commented Dec 1, 2014

Hi All,

I am getting the "505 HTTP Version Not Supported" error when I am doing some operations with my REST API. I checked the code by putting few io:write but it seems to me this error is originating from the cowboy code and I am debugging the code now. If anyone has experience this before and have a fix for this please share it with me.

GET /rest/account/image/03132ffc-67de-11e4-9c63-b13d0000008c?m=asdsda HTTP/1.1
Host: localhost:8443
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0
Accept: image/png,image/;q=0.8,/*;q=0.5
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Referer: http://localhost:8443/myaccount_page
Cookie: SESSION_ID=050903e97ecb88d5f483fb69864f7cb0
Connection: keep-alive

HTTP/1.1 505 HTTP Version Not Supported
connection: close
server: Cowboy
date: Sat, 29 Nov 2014 18:55:31 GMT
content-length: 0

Thanks & Best Regards,
Nuwan

@essen

This comment has been minimized.

Show comment
Hide comment
@essen

essen Dec 1, 2014

Member

The only place Cowboy does this is at the very beginning of parsing a request. If the request is good (and it probably is if it's Firefox), then the problem most likely lies in your code.

This kind of issue could occur if for example you do not keep track of the Req object, discarding useful information for Cowboy to properly detect whether the request has been fully read or not. This usually happens if a previous request on the same connection had a body.

If not that, then I am not sure at this point.

Member

essen commented Dec 1, 2014

The only place Cowboy does this is at the very beginning of parsing a request. If the request is good (and it probably is if it's Firefox), then the problem most likely lies in your code.

This kind of issue could occur if for example you do not keep track of the Req object, discarding useful information for Cowboy to properly detect whether the request has been fully read or not. This usually happens if a previous request on the same connection had a body.

If not that, then I am not sure at this point.

@aoeking

This comment has been minimized.

Show comment
Hide comment
@aoeking

aoeking Dec 1, 2014

Thanks for the prompt response @essen. I checked the trace that I took during that time and found out that it uses the same connection for upload a file and make the problematic request. So the error should be in the previous request and not in new request according your comment. Let me have a look at the code again and get back to you.

aoeking commented Dec 1, 2014

Thanks for the prompt response @essen. I checked the trace that I took during that time and found out that it uses the same connection for upload a file and make the problematic request. So the error should be in the previous request and not in new request according your comment. Let me have a look at the code again and get back to you.

@aoeking

This comment has been minimized.

Show comment
Hide comment
@aoeking

aoeking Dec 19, 2014

I check the application and found out that there was a place where I have ignored the Request record and reply with the original Request. Once I change that the issue got solved. Thanks for the hint @essen

aoeking commented Dec 19, 2014

I check the application and found out that there was a place where I have ignored the Request record and reply with the original Request. Once I change that the issue got solved. Thanks for the hint @essen

@essen

This comment has been minimized.

Show comment
Hide comment
@essen

essen Dec 19, 2014

Member

Cool, glad to know. That kind of issue should be a lot less frequent with upcoming 2.0 as you need to keep track of Req with a lot less functions. I should probably look into making an analysis tool to make sure people don't mess up...

Anyway closing this as this particular issue is solved. Enjoy!

Member

essen commented Dec 19, 2014

Cool, glad to know. That kind of issue should be a lot less frequent with upcoming 2.0 as you need to keep track of Req with a lot less functions. I should probably look into making an analysis tool to make sure people don't mess up...

Anyway closing this as this particular issue is solved. Enjoy!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment