httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 8431] - AddHandler/Action not-found when file does not exist
Date Tue, 23 Apr 2002 21:17:37 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=8431>.
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=8431

AddHandler/Action not-found when file does not exist

slive@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|program directory           |AddHandler/Action not-found
                   |                            |when file does not exist



------- Additional Comments From slive@apache.org  2002-04-23 21:17 -------
I'm not really an expert with this stuff, but I think the behavior you describe
in Apache 2.0 is much better than what happened in 1.3.  I think the change was
deliberate.  AddHandler is used to associate handlers with files that actually
exist.  If the file does not exist in the web space, it it completely correct
to return a 404 error.

If what you want is for every request that ends in .fwx to be fed to your script,
Apache provides lots of different ways to do that.  For example:
ScriptAliasMatch (.*)\.fwx$ c:/.../cgi-bin/foxweb.exe
AddHandler is *not* the correct way to accomplish that.

I'll leave this report open in case someone who knows this stuff better than
me can find something I'm missing.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message