Closed
Bug 73276
Opened 24 years ago
Closed 24 years ago
META HTTP-EQUIV="Refresh" not re-directing properly
Categories
(Core :: Networking, defect)
Tracking
()
People
(Reporter: tever, Assigned: gagan)
Details
Attachments
(1 file)
647 bytes,
text/html
|
Details |
Overview Description: META HTTP-EQUIV does not build the proper re-direction
string in the attached test case.
Steps to Reproduce:
1.) Load the test html file which contains the META tag
<META HTTP-EQUIV="Refresh" CONTENT="60;
/eshare/server?action=3&u=a&p=mF7CRG&c=132&%3a16664">
Actual Results:
After 60 seconds the following http command is sent.
"GET /eshare/3&u=a&p=mF7CRG&c=132&%3a16145 HTTP/1.0"
... the "server?action=" part of the string disappears.
Expected Results:
"GET /eshare/server?action=3&u=a&p=mF7CRG&c=132&%3a16145 HTTP/1.0"
Build Date & Platform Bug Found:
WinNT 2001032204
Reporter | ||
Comment 1•24 years ago
|
||
Reporter | ||
Comment 2•24 years ago
|
||
note - fixing this will make ns6 compatible with a key tool used by AOL for
supporting online help requests
![]() |
||
Comment 3•24 years ago
|
||
The problem is that the HTTP-EQUIV="REFRESH" tag should have:
CONTENT="time; URL=stuff"
Note the 'URL=' part. We are assuming that the URL to be redirected to is
everything after the first "=" character, which in this case is
"3&u=a&p=mF7CRG&c=132&%3a16664". This is interpreted as a relative URI with
respect to /eshare/ ....
![]() |
||
Comment 4•24 years ago
|
||
Duplicate of a bug that has a patch that fixes all this...
*** This bug has been marked as a duplicate of 45143 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 5•24 years ago
|
||
verified dup, I completely forgot about that one.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•