Re: 4.0.7 Release [Critical Bugs]

JM>> We support lots of broken features in IE and NS file uploads and other JM>> special cases, it might be a nice idea to try JM>> and support this too as it saves the user having to worry if the returned JM>> header is correct or not. (perhaps persume a I think supporting broken servers does nothing good. We have HTTP. Any server that is not speaking HTTP should not be called by http:// URL. Supporting such servers means encouraging broken design - look at sad story of HTML to see what happens when you support broken features. RFC says: After receiving and interpreting a request message, a server responds with an HTTP response message. The first line of a Response message is the Status-Line, consisting of the protocol version followed by a numeric status code and its associated textual phrase, with each element separated by SP characters. No CR or LF is allowed except in the final CRLF sequence. internic doesn't do that. Internic is broken. Somebody has to contact their webmaster and ask them to fix their server, so that it would serve HTTP and not something else. JM>> What do others think? I feel as long as it doesnt break anything JM>> else then we should do our best to support it, internic.net is JM>> running Apache 1.3.12 so by not support that, even if Apache is JM>> broken in this respect then we are making it impossible to use JM>> this feature on 60% or so of webservers. If it's apache that is broken then Apache should be fixed, for the start. Putting the bugs under the carpet is never a good idea. I, personally, however, don't think it's Apache - I never saw it to return HTTP response without the header. I guess that's Internic unique invention to not return HTTP status and headers. I am not sure if you even can configure Apache to do this. -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115