Forum Moderators: phranque

Message Too Old, No Replies

web site works with IE but garbled with FireFox (I broke something)

problem cause by update to Apache gone wrong

         

TheGreen

8:14 pm on May 17, 2005 (gmt 0)

10+ Year Member



My site <snip> has been working fine since last year. I recently did some updates to my system and now the site no longer works in FireFox. It does work fine in IE.

The big problem was I updated my server (Mandrake 10) using the wrong sources (yeah I am a dummy) so I evidently ended up upgrading parts of Apache, and some others I think failed. I have a few very long text files that show my failed dependencies.

Therefore, I must be missing something. I probably will reinstall, but the site has been solid for so long. I had really only meant to apply security updates.

I suspect a problem with compression, cache or MIME type but I cannot seem to figure it out. Could someone who has FireFox and IE look and see what I mean, and maybe shoot some ideas at me? As I said it has worked fine since last November. I am running it on Mandrake 10.0 official, using postnuke with Apache2 and MySQL if that matters.

I am posting here in case someone has seen this “garbled” display before and might have a clue where to start.

Quick edit: if I go to a link in the site it works (sometimes) in FireFox... <snip>

Bottom line is I broke it, but I would love to fix it, just to see if I could. I dont mind the re-install, its just that makes me feel really stupid :-)

Any ideas welcome. Thanks again.

[edited by: jdMorgan at 9:42 pm (utc) on May 17, 2005]
[edit reason] No URLs, please. See TOS. [/edit]

calmchess

9:29 pm on May 17, 2005 (gmt 0)

10+ Year Member



I don't see a problem with your website in firefox.

TheGreen

9:42 pm on May 17, 2005 (gmt 0)

10+ Year Member



Wow really?

so if you go directly to <editide by thegreen Guess I cant do that.> it works?

I have had several folks test it and they all reported it broken in ff and its a mess on mine as well. That is intersting.

[edited by: TheGreen at 9:48 pm (utc) on May 17, 2005]

TheGreen

9:43 pm on May 17, 2005 (gmt 0)

10+ Year Member



[edited by: jdMorgan at 9:42 pm (utc) on May 17, 2005]
[edit reason] No URLs, please. See TOS. [/edit]

jdMorgan Sorry about that. Is it ok to ask someone to check my site to see the problem? If so do I just spell it out? I will go read the TOS. Sorry again.

TheGreen

9:47 pm on May 17, 2005 (gmt 0)

10+ Year Member



OK, I read the TOS. Sorry again. I guess that means I cannot show someone the problem I am having, so I am not sure that this thread is meaningful anymore.

jdMorgan

12:27 am on May 18, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



It is more useful to describe the problem in words, so that 'the answer' -- if one is found -- will be useful to other members searching the archives, even if you change your domain name, or sell your site, or anything else that might 'break' the link to your site in the future.

You might want to use a server headers checker [webmasterworld.com] to check the response headers sent by your server, and use a browser headers checker [searchengineworld.com] to see what headers Firefox is sending with requests (and compare to those sent by IE).

This is probably the best first step when looking at MIME-type/compression/character-set-type problems.

Based on calmchess's response above, I would suspect either a compression or character-set problem with your new configuration, especially if you are using anything except the ISO-8859-1 character set.

Jim