287632 - Problems with rendering CSS using SSL, no problems without SSL on the same site.

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Florian Schaper]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050321 Firefox/1.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.7.6) Gecko/20050321 Firefox/1.0.2

The rendering of the page http://www.worksheetserver.com/page.htm is correct.
Visiting the same site using SSL https://www.worksheetserver.com/page.htm breaks
the table rendering.

Reproducible: Always

Steps to Reproduce:
1. Visit http://www.worksheetserver.com/page.htm, looks fine
2. https://www.worksheetserver.com/page.htm turns out broken
3.

Actual Results:  
Rendering of the site is broken using SSL

Expected Results:  
Performed like it did without encryption.

Comment 1

[Matthias Versen [:Matti]]

looks identical in Mozilla/5.0 (Windows; U; Windows NT 5.2; de-DE; rv:1.8b2)
Gecko/20050324.

Did you try a shift+reload for the broken page ?

Comment 2

[Florian Schaper]

Shift + Reload, using SSL, sometimes displays the page correctly ( one out of
three ) and the next time it is broken again. The unencrypted connection has no
problems whatsoever.

Comment 3

[Kristian Raue]

seems to be a timing problem, maybe depending on the speed of internet
connection. Sometimes the broken page appears right away, sometimes you have to
reload the https-link 10 to 20 time before the problem is visible. Strange, but
the bug is definetely reproducible.

Comment 4

[Matthias Versen [:Matti]]

Did you modify the cache preferences in your Firefox profile ?
Can you test a new profile and a recent trunk build (1.0.2 is from an old branch).

I tried it several times and it still looks ok every time...

Comment 5

[Florian Schaper]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050330
Firefox/1.0+

I could not reproduce the problem with the current nightly build. 
Everything works out for me now.

Comment 6

[Matthias Versen [:Matti]]

no patch = not fixed

Comment 7

[Matthias Versen [:Matti]]

-> wfm

Comment 8

[Krzysztof Pawlik]

Same here - 1.0.4:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050707 Firefox/1.0.4

Comment 9

[Krzysztof Pawlik]

Attachment: bugzilla2.png

Correct view of b.g.o.

Comment 10

[Krzysztof Pawlik]

Attachment: bugzilla.png

Page with missing CSS.

Comment 11

[Matthias Versen [:Matti]]

>Same here - 1.0.4:
That's is worksforme. It's a problem on your side.
Please use for example the mozillazine.org Forums for support questions.

Comment 12

[Krzysztof Pawlik]

(In reply to comment #11)
> >Same here - 1.0.4:
> That's is worksforme. It's a problem on your side.

Like?

> Please use for example the mozillazine.org Forums for support questions.

Hm... I'm not seeking support, I'm reporting a problem. I've searched the
bugzie, and found some similiar problems (like bug #221974, bug #222457). Some
were closed (like this) as WFM.

Comment 13

[Kristian Raue]

Attachment: Bitmap "broken.jpg"

Comment 14

[Kristian Raue]

Attachment: Bitmap "notbroken.jpg"

Comment 15

[Kristian Raue]

This is not easy to reproduce, but the bug is still there! But it depends on the
connection that you are using. It must be a timing problem. Please do not (!!)
set the status of this bug to RESOLVED only because it works with your
connection. If it works with your internet connection, than you are lucky (for a
time), but for other people the bug is still there. 

We are using a very fast 3Mbit DSL connection. Please look at the bitmaps
"broken.jpg" and "notbroken.jpg". If I see "broken.jpg" I simply press RELOAD a
few times and suddenly I see "notbroken.jpg".

The problem seem to have been fixed with some of the nightly builds, but was
never resolved on any of the offical releases. Very annoying.

Comment 16

[Florian Schaper]

Getting the same result as Mr. Raue.

Comment 17

[Matthias Versen [:Matti]]

I set it to resolved and it works works for thousands of users.

>The problem seem to have been fixed with some of the nightly builds
That's enough to mark it WORKSFORME again. The Gecko in FF1.0.X is over 12+
months old and we don't accept Gecko bugs for such old builds unless you have a
bug where many users are affected. FF1.0.5 is basicall FF1.0 + additional
security fixes but nothing more.

Please reopen this if you get this problem with a recent trunk build (such as
Deer Park Alpha) and a new Firefox profile.