Bugs item #1013752, was opened at 2004-08-22 04:16
Message generated for change (Comment added) made by dvrsn
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=103152&aid=1013752&group_id=3152

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: API: C
Group: aolserver_v40
Status: Open
Resolution: None
Priority: 6
Private: No
Submitted By: Stephen Deasey (sdeasey)
Assigned to: Nobody/Anonymous (nobody)
Summary: Invalid response status logged for custom redirects

Initial Comment:

When using custom redirects, e.g.

  ns_section "ns/server/${servicename}/redirects"
  ns_param   404   "/notfound.adp"

If notfound.adp exists (which it should) then the
client is served with a 200 response code, which also
end up in the access log.  Same for all redirects.

This patch reverts the default status code to 200 in
driver.c when a fresh Conn is set up.  It explicitly
sets responseCode in ReturnRedirect.  And it explicitly
does not set a response code of 200 when constructing
headers.  200 should be inherited from a fresh Conn,
and we don't want to disturb anything the custom
redirect handler just set.



----------------------------------------------------------------------

Comment By: Jeff Rogers (dvrsn)
Date: 2011-09-15 14:37

Message:
I think this is out of date.

The Ns_ConnSetStatus() / [ns_conn status] api calls were added in 2005
which allow any page to set its own return status.  The "notfound.adp" page
can use that to indicate a 404 status.  

Suggest closing as won't fix.

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=103152&aid=1013752&group_id=3152