Welcome to the MacNN Forums.

Jool · Jan 16, 2003, 12:52 AM

At work(local newspaper) we are using NT 4 with Netscape Enterprise Server 3.5.1 for our newspaper archive, I know it's not the best server but it works fine and does it's job. The only problem is that everytime I try to access the server with Safari the server goes down and I have to click "cancel" on "dr.watsons" very informative popup, then the server works fine again.

Is there anyone else out there using NES 3.5.1 who can confirm this?

/Jonas

moki · Jan 16, 2003, 02:06 AM

If a browser can crash a server, the fault is absolutely with the server. There's no way a robust server should ever be able to be crashed by a client.

I suggest checking to see if there are any upgrades or patches for it.

Jool · Jan 16, 2003, 02:33 AM

The thing is that any other browser works fine with that server and we are probobly not going to upgrade it just so we can use Safari, I guess it's to early to trash IE.

/Jonas

Xeo · Jan 16, 2003, 02:34 AM

How could it be possible that a server would crash as a result of the client. The client says, "Hey server, I need a web page." All clients must do that the same way, right? Then, Mr. Server sends out the web page and all the related content and it's up to the browser to sit there and render it, locally, without needing to send anything to the server.

It makes no sense to me.

Xeo · Jan 16, 2003, 02:36 AM

Originally posted by Jool:
The thing is that any other browser works fine with that server and we are probobly not going to upgrade it just so we can use Safari, I guess it's to early to trash IE.

/Jonas

The problem with that philosophy is that you expect none of your readers to use Safari. Can your server last long enough to deny content to Safari's User Agent? Even if you do that, the User Agent can still be changed and then you're screwed.

Honestly, one word: Apache. It's free. It works.

Jool · Jan 16, 2003, 03:19 AM

The server is only used internaly for searching old articles(maby not the right word but I think you know what I mean), our main webserver runs Apache.

I know that the crashing sounds strange but I have used many different browsers(if not all) and as soon as I hit return-button in Safari the server goes down.

It's easy to say "upgrade to Apache or whatever" but it's not so easy to convince my boss to buy a new solution just so we can use Safari, it's easier to keep using IE. It's not a big problem yet because were only 3 of about 250 people using OSX but if we decide to move to OSX all over then we maby have to do something about it.

/Jonas

TC · Jan 16, 2003, 03:26 AM

Have you tried using the Debug Menu in Safari to get it to declare itself as another browser?
Only thinkg I can think of is that the Netscape server has problems with the length of the Safari identification string.

Also, you don't have to convince your boss to buy another solution, apache is free.

Have you looked at the log files of the server to see exactly what requests safari is sending when it crashes? Obviously it might crash before writing them out but you might be lucky. If it is a problem with safari sending strange requests then you could let Apple know, hell you should let them know anyway.

Xeo · Jan 16, 2003, 03:40 AM

Originally posted by Jool:
The server is only used internaly for searching old articles(maby not the right word but I think you know what I mean), our main webserver runs Apache.

Well internally is a whole different matter. I didn't realize that. You're right, it's easier just to not use Safari for now. Find out what happens when Safari goes final. Then you can worry about maybe upgrading.

Jool · Jan 16, 2003, 03:56 AM

The first thing I did was sending that bugreport to Apple. I can try Safari Enhancer and see what happens and I'll check the logs to but I did that before and it didn't tell me much.

Moving to Linux/Apache would be nice but this archive-server depends on other servers to work and it's not that easy but ofcourse it can be done.

/Jonas

GoGoReggieXPowars · Jan 16, 2003, 09:01 AM

Originally posted by Xeo:
client says, "Hey server, I need a web page." All clients must do that the same way, right

Except for IE

Sarc · Jan 16, 2003, 11:26 AM

Do you have a Linux box at work ?
If so you could try to access the server using Konqueror (basically same engine as Safari) and see if the server goes down ...

voodoo · Jan 16, 2003, 07:28 PM

Originally posted by GoGoReggieXPowars:
Except for IE

*lol* good read!

Maybe the author is on to something. This would be a simpler faster way for IE to receive data.

Superchicken · Jan 16, 2003, 09:25 PM

That is offically great.... gota love how microsoft just LOVES screwing over everyone.

Jool · Jan 16, 2003, 11:29 PM

I tried Konqueror 2.x and it worked fine. I haven't tried Lynx or Links yet but I think they will both work without crashing our poor server.

Enable the bug-menu and playing around in that didn't work either.

/Jonas

someone_else · Jan 17, 2003, 12:43 AM

Originally posted by Jool:
I tried Konqueror 2.x and it worked fine. I haven't tried Lynx or Links yet but I think they will both work without crashing our poor server.

Enable the bug-menu and playing around in that didn't work either.

/Jonas

The Safari code is based off KDE 3.0.x (I don't know if Kong 2.x is in KDE 3.0.x).

Anyway, I think another poster had it right. There is probably some buffer overflow somewhere. But I doubt if it's the UA string, Chimera has a longer UA string than Safari. Have you tried Chimera?