rob Reporter
	Description • 23 years ago

A "content-encoding: gzip" page has a CRC.  If the CRC is wrong, Mozilla
silently ignores it.  Netscape 4 displays a pop-up about a network error. 
Internet Explorer displays a blank page (haha).

(If needed, I can setup a server that produces a wrong CRC for gzip-encoded pages.)

My opinion is that a notification to the user should be displayed about some
type of problem occuring.  Should anything be displayed?  Is it better to have
something "wrong" displayed than nothing at all?

1.0RC2, Windows2000.

	Boris Zbarsky [:bzbarsky]
	Comment 1 • 23 years ago

Setting up that server would be a great boon to fixing this bug (testing fixes
is always nice).

	rob Reporter
	Comment 2 • 23 years ago

I set up a server with bad CRC's.

http://rekl.yi.org/crctest/ works correctly.
http://rekl.yi.org:8081/crctest/ generates bad CRC's.

More detailed info is available on that server.

	Darin Fisher
	Comment 3 • 23 years ago

mass futuring of untargeted bugs

	Christian 'CeeJay' Jensen
	Comment 4 • 20 years ago

The QA contact on this bug can't possible still be correct

	benc
	Comment 5 • 20 years ago

->default qa

	Darin Fisher
	Comment 6 • 18 years ago

-> default owner

	Patrick McManus [:mcmanus]
	Comment 7 • 9 years ago

bagder looked into this and it turns out many gzip encodings lack the terminating blocks and general correct formatting. enforcing the crc is just a recipe for not displaying content we could otherwise render