DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27770>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27770 MultiViews and RequestHeader Summary: MultiViews and RequestHeader Product: Apache httpd-2.0 Version: 2.0.48 Platform: PC URL: http://tranchant.plus.com/top OS/Version: Linux Status: NEW Severity: Normal Priority: Other Component: mod_headers AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I'm trying to implement MultiViews to avoid using filename extensions. It works well, except when certain user agents (typically crawlers) try to access a non-extensioned URI that MultiViews resolves to a PHP file. When the UA sends an Accept header of, say, "text/*", MultiViews reads the .php file as being of type application/x-httpd-php (due to the PHP AddType line), and returns a 406 Not Acceptable error. Of course, a processed .php file leaves the server as text/html (for example), but MultiViews doesn't know this. I thought I could get around this using RequestHeader to add "application/x-httpd-php" to the incoming Accept header, but it seems that MultiViews fakes up its type map based on the original Accept header, not the modified one. There may be other preferred ways to fix this, but asking MultiViews to use the modified header would seem to make sense, and I suspect it would fix this problem. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
