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=17936>. 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=17936 Does not return HTTP 406 for restricted client Accept headers ------- Additional Comments From [EMAIL PROTECTED] 2003-03-13 18:27 ------- Thank you for your quick response André. Ongoing, I'll just update this bug rather than have us go back and forth with the same stuff on both bugs. 17937 references this bug, and that is enough. Your premise is that negotiation will not be invoked if there exists only one resource for the requested file, and that the correct thing would be to return the requested file, disregarding the client's Accept headers. It would help me to accept this, if you could show some public documentation that would back this type of response. I have done my best to comb through relevant documentation, and to do searches for non-negotiation criteria. I'm going to take some time to research this some more, while also discussing it with others. I'm afraid that I'm still not convinced that Apache httpd is exhibiting the correct behavior. Although, I will submit that I have seen both behaviors in other web servers. IIS does return a HTTP 406, and I admit that that does not make it "correct". Apache Tomcat (coyote) does the same as Apache httpd, but coming from the same group that is not a surprise. However, when this is compounded by SUN's Enterprise web server also not returning a HTTP 406, I must then be able to supply further evidence that would support returning HTTP 406 in this case. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
