Closed
Bug 222673
Opened 22 years ago
Closed 22 years ago
No redirect using META tag
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: rvjanc, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
|
347 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.5) Gecko/20031007
The following TAG at a secure site doesn't perform the redirect
<META http-equiv="refresh" content="0; url=pgLoginNew.jsp">
The HTML code just shows up in the browser window. I tried this using IE,
Safari, Camino and Firebird. It works properly in IE and Safari but doesn't
work in Camino or Firebird (no surprise I guess). I know that the HTML standard
discourages this technique but it is in the standard.
bob
Reproducible: Always
Steps to Reproduce:
1.Click logout
2.The HTML shows up in the window and there is no redirect
3.
Actual Results:
The HTML shows up in the window
Expected Results:
Initial login window should return
|
||
Comment 1•22 years ago
|
||
Check the Page Info for that page and see what the "Type" field reads.
Your description sounds like it's going to say "text/plain" or something besides
"text/html" which would make Mozilla render the page as plain text instead of HTML.
|
||
Comment 2•22 years ago
|
||
according to:
http://wp.netscape.com/assist/net_sites/pushpull.html
Important note: make sure the URL you give is fully qualified (e.g.
http://whatever/whatever). That is, don't use a relative URL.
Here is the whole page
<!DOCTYPE HTML PUBLIC "-//Metrius//DTD Metrius Transitional//EN"
"http://www.motorola.com/General/DTDs/motorola_transitional.dtd">
<META http-equiv="refresh" content="0; url=pgLoginNew.jsp">
<html>
<head>
</head>
<body>
</body>
</html>
|
|
||
Comment 4•22 years ago
|
||
Again, when you are on that page and look at Page Info, what does it read for
"type"?
I doubt we will get much just from looking at the source code.
|
||
Comment 5•22 years ago
|
||
The meta element should be inside the head element according to the HTML
specification.
|
|
||
Comment 6•22 years ago
|
||
While comment 5 is correct, Mozilla (and other browsers) will let you get away
with it. I think in Mozilla's case, it's to not break the multitude of sites
that use the meta tag wrong. There's a bug on in somewhere that documents it.
If the source code is showing up in the window, the page is probably served
wrong. A misplaced meta tag can't cause that. Attaching testcase.
|
|
||
Comment 7•22 years ago
|
||
Testcase will refresh, does not render source code.
|
|
||
Comment 8•22 years ago
|
||
WFM: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20031011
Should be marked as invalid/WFM. Submitter can go to a forum for questions about
MIME-types, bugzilla is for bugs.
Soory I misunderstood your question. The type was text/plain
bob
|
|
||
Comment 10•22 years ago
|
||
That's why you're seeing source code and no refresh then. The server is saying
it's plain text, so Mozilla treats it as such.
Whoever administers the server needs to correct the setting.
->Invalid
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
|
||
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•