Re: mySQL error depending on browser

On Tue, 31 Aug 2004 13:04:48 +0200
Bèr Kessels <berdrupal@xxxxxxxxxx> wrote:

> Hi,
> 
> It seems your web does not work(s) too well atm :) (sorry could not
> resist)+

:( bha fortunately it is still not in production and as a not so good
excuse I'm not the sysadmin once in my life. But the guy managing the
box has been very kind at least, not only installing drupal but also
trying to solve this mess.

> > It is not that w3m always succeed in getting the page, but it does
> > it more often. w3m use HTTP 1.0, Konqueror and FireFox HTTP 1.1
> > If I'm visiting the site from a completely different ISP I still
> > have to observe the problem.

- Let me rephrase. I didn't observed the behaviour with IE surfing from
netvigator.com and fastweb.it. That could be just accidental.

- I rarely observed the behaviour with w3m surfing from netvigator.com.

- I observed this behaviour surfing with Konqueror and FireFox from
netvigator.com.

- I never observed this behaviour with w3m surfing from tin.it.

- friends didn't report any error with Konqueror and Firefox, but they
didn't test extensively

I can't test extensively from another connection cos at the moment I
don't have a remote box with X installed.

After further testing I wouldn't consider the browser as a trigger.

> This ,and the "random" part made me think of something else. What if
> you have several problems, one being wrong headers sent and the other
> one being some php-mysql-server problem.
> 
> The first one, the headers, /could/ be due to cache in either drupal
> itself or in some proxy. Did you try turning off cache in drupal?

Drupal cache is off.

I dumped some traffic from me and the server using tin.it and
netvigator.com connections and there are no differences in HTTP headers
when I get the error and when I don't get it.

I'm starting to think there was a mysql error and netvigator proxies
(set up in a strange way actually) amplified the problem.

mysql will be kept under control by the "man in charge" (and that's not
me).

Is there any way to tweak drupal to send custom http header? It could
come handy for very dynamic pages that shouldn't be cached.

:( wasted half a day and I'm still not sure what's going on. Fortunately
now it is working and I hadn't seen an error in several hours.



thx for the support... and the humor ;)

--
[ Drupal support list | http://list.drupal.org/ ]