228782 - view source is blank if page has no HTTP Content-Length header, and page is in the process of being sent

Status: RESOLVED EXPIRED

(Core Graveyard :: View Source, defect)

Description

[Chua Chee Wee]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.6a) Gecko/20031030
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.6a) Gecko/20031030

If a page is *being* served, and the HTTP server did not send a content-length
header (indicating unknown length), then, while the page is being served, 
view source will always be blank, since it is attempting to get a live source.

Please 

Reproducible: Always

Steps to Reproduce:
1. Create a HTTP server that sends say, 1 byte of data every second.
2. When the HTTP server sends the HTTP header before sending the data, ensure
that the Content-Length header is not sent.
3. Use Mozilla to browse the page.
4. View Page/Frame Source will be blank.
Actual Results:  
View Page/Frame Source is blank

Expected Results:  
Instead of browsing the URL again when the View Page/Frame Source is issued,
it should view the page/frame source from the cache itself.

ie, my understand is that, given URL A, Mozilla fetches the contents of A and
stores into cache B. However, when View Page/Frame source is issued, Mozilla
attempts to get the contents of A again, to display into the view page/frame
source window. Why doesn't it just read B, and display it, since B is the local
data?

Comment 1

[Sean Umphlet (nosebleed)]

I think that pipelining being enables MAY have something to do with this.

However, I can't find a server that sends only 1 byte of data a second. The URL
you provided seems to not do this...

I also have pipelining enabled.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031217

Comment 2

[Chua Chee Wee]

Attachment: Shows where to invoke view source

Shows where to invoke View Source on the URL at
http://www.rightsecurity.biz:81/

Note: You have to enter a nick to go into the site first.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.