axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18561] - SSL Tunneling via MS-Proxy 2.0 does not work; bad response from proxy
Date Wed, 02 Apr 2003 18:00:23 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18561>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18561

SSL Tunneling via MS-Proxy 2.0 does not work; bad response from proxy





------- Additional Comments From stevel@apache.org  2003-04-02 18:00 -------
I think you should report it to them. If they didnt read the spec before they
shipped, it is their responsibility to support it. Really, you paid for the
privilege of the support calls, and you should exercise them. Their response
will either be 'here is a service pack' or 'upgrade, you havent given us enough
money recently'.

My reading of the response section,
http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6 says

 Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF


So by putting two spaces in, they are breaking the rules. We could handle it in
axis, but I'd like to see what the MS proposed solution to their defect is
first, as there are probably plenty many other apps that will encounter the same
problem.

Mime
View raw message