DiabloFans

I'm more a fan of Green Tea with a spot of Honey. *drools*

Just to let everybody know, here is an explanation of 504 timeouts: (source)

[spoil]HTTP Error 504 Gateway timeout

Introduction

A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.

This usually means that the upstream server is down (no response to the gateway/proxy), rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.

504 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:

Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '504'.
[/spoil]

It depends on when the timeout occurs. I've noticed that it's six of one, half a dozen of the other for me.

You see... posting is, at base, a two-part execution. 1) (client) Send info -> (server) receive info -> (s->c) acknowledge receipt -> (s) write info ---- (after success) 2) (server) Send write acknowledgement + new page -> (c) receive new page

At any point in that scheme after "receive info", if the server times out, the post will have been made, however, if it happens before that, no go on the post....o.

Hope that helps!

I'm getting them on the Mac. I'm wondering if, with the recent spambots hitting, if the site is under some brute-force attacks that are muddling the server up.