Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 21357 invoked by uid 6000); 12 Jul 1999 02:20:11 -0000 Received: (qmail 21272 invoked by uid 2001); 12 Jul 1999 02:20:00 -0000 Received: (qmail 17349 invoked by uid 2012); 12 Jul 1999 02:11:01 -0000 Message-Id: <19990712021101.17348.qmail@hyperreal.org> Date: 12 Jul 1999 02:11:01 -0000 From: George Michaelson Reply-To: ggm@dstc.edu.au To: apbugs@hyperreal.org X-Send-Pr-Version: 3.2 Subject: documentation/4720: example of 302 Redirect can't work for IE3.0 Sender: apache-bugdb-owner@apache.org Precedence: bulk >Number: 4720 >Category: documentation >Synopsis: example of 302 Redirect can't work for IE3.0 >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: open >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Sun Jul 11 19:20:00 PDT 1999 >Last-Modified: >Originator: ggm@dstc.edu.au >Organization: apache >Release: current >Environment: any IE3.0 browser >Description: the apache document: http://www.apache.org/docs-1.2/misc/howto.html#redirect has an example Perl redirector: #!/usr/local/bin/perl print "Status: 302 Moved Temporarily\r Location: http://www.some.where.else.com/\r\n\r\n"; but IE3.0 fails because the \r embedded instance is not parsed correctly. Also, a literal leading-space in a Header: field is often interpeted in RFC-land as meaning a continuation line, and not a new Header instance in itself (eg SMTP/NNTP) Additionally, print appears to collide with other Header: instances and the output datastream is not well-formed. >How-To-Repeat: try browsing onto any site using this syntax, where Apache is emitting Date: and Server: headers as well, and test with IE3.0 as well as Netscape 4.0 and IE4.0 clients >Fix: use printf STDOUT "Status: 302 Moved Temporarily\r\nLocation: http://www.some.where.else.com/\r\n\r\n"; this appears to fix the \r problem, and also ensures the write to output is a single event which is not interrupted by any other header: lines. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]