Re: Can I configure Tomcat to send HTTP/1.1 200 OK rather than HTT P/1.1 200?
I have a really picky browser that is expecting the OK after 200 when receiving HTTP response as: out of curiosity, which browser is this? Might save me some bug-tracking headaches later. Jason Hua Hou wrote: I have a really picky browser that is expecting the OK after 200 when receiving HTTP response as: HTTP/1.1 200 OK Without the OK, the browser can NOT render the HTTP response correctly. I have two questions: (1) Is there a way to configure Tomcat to send OK after the 200 code when sending response header to browser? (2) According the HTTP 1.1 spec, is the OK required after the 200 code? Thank you very much for your great help! Hua - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can I configure Tomcat to send HTTP/1.1 200 OK rather than HTT P/1.1 200?
Thank you for your reply. I am using Tomcat 4.1.24 and have to recompile the code to append the reason phrase. Thanks again. Hua -Original Message- From: Tim Funk [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 21, 2003 5:03 PM To: Tomcat Users List Subject: Re: Can I configure Tomcat to send HTTP/1.1 200 OK rather than HTT P/1.1 200? Recompile the source. (But I thought the 4.1.27 also appended the status text too) http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6 The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's, are presented below. The reason phrases listed here are only recommendations -- they MAY be replaced by local equivalents without affecting the protocol. So OK is only a recommendation. It may actually be any word based on locale. So the following is probably also valid: HTTP/1.1 200 Roger -Tim Hua Hou wrote: I have a really picky browser that is expecting the OK after 200 when receiving HTTP response as: HTTP/1.1 200 OK Without the OK, the browser can NOT render the HTTP response correctly. I have two questions: (1) Is there a way to configure Tomcat to send OK after the 200 code when sending response header to browser? (2) According the HTTP 1.1 spec, is the OK required after the 200 code? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can I configure Tomcat to send HTTP/1.1 200 OK rather than HTT P/1.1 200?
Recompile the source. (But I thought the 4.1.27 also appended the status text too) http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6 The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's, are presented below. The reason phrases listed here are only recommendations -- they MAY be replaced by local equivalents without affecting the protocol. So OK is only a recommendation. It may actually be any word based on locale. So the following is probably also valid: HTTP/1.1 200 Roger -Tim Hua Hou wrote: I have a really picky browser that is expecting the OK after 200 when receiving HTTP response as: HTTP/1.1 200 OK Without the OK, the browser can NOT render the HTTP response correctly. I have two questions: (1) Is there a way to configure Tomcat to send OK after the 200 code when sending response header to browser? (2) According the HTTP 1.1 spec, is the OK required after the 200 code? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
