11

I have already googled that 505 is "HTTP Version not supported", but still can not figure out my problem. I have a web application with Tomcat,server side with self-signed certificate to enable HTTPS,without authenticating client. The client will authenticate server certificate. I have analyze the wireshark packet, it seems the SSL handshark is correct. But when i check Tomcat localhost_access_log,there will be an 505 error for the client request, also server side does not receive the client request. Could you kindly help to give some hint on this?

172.25.21.113 - - [24/May/2012:16:28:26 +0800] "GET /updserver/update?action=signature_update&device_type=NGN&service_type=KAV&engine_ver=1.00&sig_ver=4.123&mac=0019CB72736E HTTP/1.1 " 505 -
Simon Wang
  • 2,235
  • 7
  • 36
  • 48
  • Is there really a space after "HTTP/1.1" in the request line? I wonder if that could be the problem. – Christopher Schultz May 24 '12 at 14:49
  • Related problem: [java.io.IOException: Server returns HTTP response code 505](http://stackoverflow.com/questions/3625659/java-io-ioexception-server-returns-http-response-code-505) – sleske May 21 '15 at 13:08

2 Answers2

16

If you make a request to Tomcat with trailing whitespace after the HTTP version (as in your example), Tomcat will respond with 505 error. Confirmed on Tomcat 7.0.27.

RFC 2616 (HTTP 1.1) says that the HTTP-Version is made up of "HTTP/" + digit + "." + digit. Request-Line ends with " " + HTTP-Version + CRLF which means no whitespace is allowed after that last digit.

References:

Christopher Schultz
  • 20,221
  • 9
  • 60
  • 77
  • yes, there is one space character at the end of line. I can not control the client, but it works well with Tomcat5.5? How to deal with such case? – Simon Wang May 25 '12 at 01:54
  • It seems our team hacked Tomcat5.5 before so it worked,maybe i need to hack Tomcat7 again to fix this issue. Great Thanks Christopher Schultz~ – Simon Wang May 25 '12 at 02:38
6

Clearly not the answer for the OP, but I ran into this error message tonight while trying to debug a SOLR server.

My problem wasn't an extra space after the HTTP version.

my client application was logging the bad URL, which i blithely copied & pasted into a telnet connection to the SOLR tomcat's http port. My log message showed the URL without properly %20-encoding a space in the URL. I got the bad HTTP version error, presumably because it was interpreting everything after the space in the URL as my HTTP version.

thanks to http://java.dzone.com/news/solr-tomcat-and-http11-505 for the hint.

Dan Pritts
  • 1,274
  • 16
  • 14