SQL Error again

[Bearded Dragon]

Seems to happen every so often. If I go to thedaobums.com it throws the error but if I go to thedaobums.com/index.php it doesn't.

[blue eyed snake]

here the same

[dawei]

If we can get an update done, there may be some security and integrity improvements.

[Kar3n]

Intermittent SQL errors or it times out.

[dawei]

Me too...  but we're both online now 

[Apech]

again today - seems to be becoming a regular thing

[blue eyed snake]

here too, several times this week   ,

that'l teach us patience 

[dawei]

Maybe some folks are just online too much          (ducking at tomatoes thrown)

 

I've tried to impress the need to upgrade the software but I'm waiting like everyone else.

[Apech]

Maybe some folks are just online too much          (ducking at tomatoes thrown)

 

I've tried to impress the need to upgrade the software but I'm waiting like everyone else.

 

 

I'm addicted - I constantly need to know if Karl has said anything irrational.

[wilfred]

a little SQL is good for the bowels

[Kar3n]

... here too, for a good chunk of the morning.

 

[already]

I've been getting this error for days but mostly when trying to access the buddhist discussion subforum.

[Marblehead]

Yeah, sometimes life gives us SQL errors.

 

The program is rigged so that the Buddhist sub-forum gets more of them than any other sub-forum.  It is a test of their patience.

[blue eyed snake]

Yeah, sometimes life gives us SQL errors.

 

The program is rigged so that the Buddhist sub-forum gets more of them than any other sub-forum.  It is a test of their patience.

 

   

[Eques Peregrinus]

I had a SQL error recently on the index page, it persisted for a few days before I tried to access to an other sub forum (by mistake while browsing my history), and the page got displayed correctly. This pushed me to experiment a bit.

 

I sniffed my traffic with Wireshark, while trying to fetch the index page which displayed an SQL error, and observed there were no connection to the server, therefore that was likely a caching problem.

 

So I tried to reload the page while bypassing the cache (generally by pressing [Ctrl] + [F5], or with developer tools) and the page reloaded normally without SQL error.

 

Normally, a web resource (html pages, images, ...) is send with an ETag* (a field in the HTTP headers) or at least an expiration date**. I suppose that these HTTP headers are missing from the server response when it has to send the SQL error page.

 

 

The same behaviour occurs for the page indicating the server is offline (the page with the guy sitting in lotus).

 

 

*In the case of the ETag, the web browser establishes a connection with the server to send the ETag, and the server responds either by telling the resource is up-to-date or with the updated resource.

 

**In the case of an expiration date, it is just a date, and the browser consults its cache until the date is reached, afterward, if the resource is requested, the browser is going to consult the server normally.