Closed Bug 241094 Opened 22 years ago Closed 22 years ago

images are not shown, because wrong link is used

Categories

(Core :: Networking, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jens-uwe, Assigned: darin.moz)

References

()

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040419 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a) Gecko/20040419 on the mentioned webpage most of the images are not shown, which make the page looking extremly ugly. The page works with older Mozilla-versions (firefox0.8, Mozila1.5) and all other browsers tested. Since it works with older Mozilla-Builds, it is a regression! The bug is probably caused by the fact, that Mozilla uses a wrong link to the picture. Mozilla: http://www.teltex.de/pages/images/logo/ss.t-mobile.gif Konqueror: http://www.teltex.de:80/images/logo/ss.t-mobile.gif Reproducible: Always Steps to Reproduce: 1. go to www.teltex.de with a rather new build 2. you can see the problematic images Actual Results: most of the pictures are not shown Expected Results: they should be shown sorry, if this is the wrong component, but the other components sounded even worse ;-)
*** Bug 241098 has been marked as a duplicate of this bug. ***
Same problem with 2004041809/trunk/W2K
Keywords: regression
OS: Linux → All
well... the workaround doesn't work because the server sends: Server: Oracle9iAS (9.0.2.2) Containers for J2EE and that specific header is not blacklisted.
Darin, your call. How opposed are you to blacklisting "Oracle9iAS"?
And this is pretty totally not parser. At best it's "dom", but I think networking applies better.
Assignee: parser → darin
Component: HTML: Parser → Networking
QA Contact: benc
(In reply to comment #6) > And this is pretty totally not parser. bug 238654 was in htmlparser... fwiw I agree with blacklisting Oracle9iAS - this is a not too popular feature, and an uncommon server
> bug 238654 was in htmlparser... Yeah, well. That was misfiled too. I just forgot to correct it.
Blocks: 238654
would probably be fixed by the patch in bug 241320
I've backed out content-location support.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.