On 2005.02.11, Stephen Deasey <[EMAIL PROTECTED]> wrote:
>
> I fixed this bug 6 months ago. There's a patch on SourceForge:
>
> "Invalid response status logged for custom redirects"
> http://sourceforge.net/tracker/?func=detail&aid=1013752&group_id=3152&atid=103152
Can you explain this:
- connPtr->responseStatus = status;
+ /* 200 is default. Don't stomp custom redirects. */
+ if (status != 200) {
+ connPtr->responseStatus = status;
+ }
What if the custom redirect isn't found (status = 404) - why should that
stomp the original (say, connPtr->responseStatus == 500)?
I'll have to play around with this and explore the various test cases to
see how it actually behaves.
> You may also be interested in this related patch which alows a custom
> redirect handler to know the original URL as sent by the browser and
> act accordingly:
>
> "ns_conn seturl newUrl"
> http://sourceforge.net/tracker/?func=detail&aid=1013672&group_id=3152&atid=353152
Why introduce Ns_ConnSetUrl()? Why not change Ns_SetRequestUrl() to do
this?
-- Dossy
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
