Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 45690 - Problems with /network/yn/errata/basic.html
Problems with /network/yn/errata/basic.html
Product: Red Hat Web Site
Classification: Red Hat
Component: Other (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Web Development
Web Development
Depends On:
Blocks: 41072
  Show dependency treegraph
Reported: 2001-06-24 17:40 EDT by Christopher Blizzard
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-18 09:49:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Christopher Blizzard 2001-06-24 17:40:50 EDT
There are several problems with this page:

1) It sends a multipart/mixed content type that includes an incomplete MIME
message.  The message ends with the closing HTML tag, not a boundry tag as
it should.

2) It sends a bad charset:

Content-Type: multipart/mixed;boundary=xxyyzzzz0011294;

3) The refresh URI isn't valid:

This is a multipart reponse in MIME format
Content-type: text/html; name=Update
Refresh: 5,url=$back_url
Title: Updating

This happens to work in Netscape because it thinks that the URI is bad and
treats it as if the url= parameter wasn't there.

It's interesting to note that there are two problems with Mozilla at the
moment as well:

If you include anything after the content type in the Content-type:
paramter of a multipart/mixed doc it isn't parsed correctly:

Content-type: text/html; name=Update

I have a patch for this that will parse it properly but if you want older
versions to work you might want to remove the ; name=Update from the
content type header.

Also, I've discovered, much to my chagrin, that the Refresh: header doesn't
work at all with multipart/mixed documents.  It doesn't matter if you
include it in the http headers or the headers of the document.  This is a
less easy fix because it's an architecture problem but I'm working on it.

I have to ask.  If the document is being truncated after the first
document, why is it using a multipart document at all?
Comment 1 Jay Turner 2001-09-18 09:49:48 EDT
What's the status of this with the new site?
Comment 2 Jay Turner 2001-09-28 11:51:45 EDT
Closing this out as we are not using any of this on the new site and things are
working pretty well with mozilla and galeon on the new site.  Will reopen if

Note You need to log in before you can comment on or make changes to this bug.