Closed Bug 166366 Opened 23 years ago Closed 17 years ago

hbl-miniaturen.de - Redirection URL dowsn't work !

Categories

(Tech Evangelism Graveyard :: German, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mh, Unassigned)

References

()

Details

(Whiteboard: [bug248549notfixed])

When opening one of the following URLs, an error occures: HBL - Home Page <http://www.hbl-miniaturen.de/> ISE HomePage <http://www.ise-software.com/> tecnotron software gmbh - Home Page <http://www.tecnotron-software.de/> The ';' is misinterpreted I think.
not a blocker bug
Severity: blocker → normal
Seeing this too on windows ... setting component and confirming
Assignee: hewitt → darin
Status: UNCONFIRMED → NEW
Component: URL Bar → Networking: HTTP
Ever confirmed: true
OS: Windows 98 → All
QA Contact: claudius → httpqa
Hardware: PC → All
I meant linux ...
The page contains this redirection: <meta http-equiv="refresh" content="2;URL=hbl.htm; text/html; charset=iso-8859-1">
This the comment from the code that parses the header (nsDocShell::SetupRefreshURIFromHeader): // Refresh headers are parsed with the following format in mind // <META HTTP-EQUIV=REFRESH CONTENT="5; URL=http://uri"> // By the time we are here, the following is true: // header = "REFRESH" // content = "5; URL=http://uri" // note the URL attribute is // optional, if it is absent, the currently loaded url is used. // Also note that the seconds and URL separator can be either // a ';' or a ','. The ',' separator should be illegal but CNN // is using it. // // We need to handle the following strings, where // - X is a set of digits // - URI is either a relative or absolute URI // // Note that URI should start with "url=" but we allow omission // // "" || ";" || "," // empty string. use the currently loaded URI // and refresh immediately. // "X" || "X;" || "X," // Refresh the currently loaded URI in X seconds. // "X; URI" || "X, URI" // Refresh using URI as the destination in X seconds. // "URI" || "; URI" || ", URI" // Refresh immediately using URI as the destination. // >>>>>>>>>>>>>>>>>>>>>>>>>>>> // Currently, anything immediately following the URI, if // seperated by any char in the set "'\"\t\r\n " will be // ignored. So "10; url=go.html ; foo=bar" will work, // and so will "10; url='go.html'; foo=bar". However, // "10; url=go.html; foo=bar" will result in the uri // "go.html;" since ';' and ',' are valid uri characters. <<<<<<<<<<<<<<<<<<<<<<<<<<<<< // Note that we need to remove any tokens wrapping the URI. // These tokens currently include spaces, double and single // quotes. // when done, seconds is 0 or the given number of seconds // uriAttrib is empty or the URI specified See the marked paragraph. This seems to be an evangelism case. Fix the site.
-> let docshell folks decide what they want to do with this bug.
Assignee: darin → adamlock
Component: Networking: HTTP → Embedding: Docshell
QA Contact: httpqa → adamlock
This seems like a WONTFIX evangelism issue to me. It's not a dupe of that other bug.
Marking WONTFIX. I believe evangelism is the best solution here.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Then it should be reopened and handed over to tech evangelism. Should be simple to fix ... just add one space before the ;. Let tech evangelism decide if it is worth the effort.
Status: RESOLVED → REOPENED
Component: Embedding: Docshell → Europe: West
Product: Browser → Tech Evangelism
Resolution: WONTFIX → ---
Version: other → unspecified
reassigning to correct owner ...
Assignee: adamlock → nitot
Status: REOPENED → NEW
QA Contact: adamlock → brantgurganus2001
Summary: Redirection URL dowsn't work ! → hbl-miniaturen.de - Redirection URL dowsn't work !
move...
Assignee: nitot → german
Component: Europe: West → German
QA Contact: brantgurganus2001 → german
[bug248549notfixed]
Whiteboard: [bug248549notfixed]
owned by domain grabber
owned by domain grabber
Status: NEW → RESOLVED
Closed: 23 years ago17 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.