Re: [Lynx-dev] Why Do I Receive a Gateway Timeout on www.crisisgroup.org

[Mouse]

> Normally 504 gateway errors have nothing to do with your personal
> setup.  Instead they reflect a communications error between the
> site's own servers, timing out communications wise.

With lynx, I see an immediate (on human timescales) HTTP/1.1 504
GATEWAY_TIMEOUT response.  With my own manual fetcher script, I see a
redirect to HTTPS.  I infer they are playing silly User-Agent: games.
Maybe telling lynx to lie in its User-Agent: header would work around
whatever is broken?

Gateway Timeout _is_ the standard meaning of 504: "The 504 (Gateway
Timeout) status code indicates that the server, while acting as a
gateway or proxy, did not receive a timely response from an upstream
server it needed to access in order to complete the request.".  I
suppose it's possible that lynx requests get redirected to a backend
that's timing out.  But the short time before I get the 504 argues
against that.  Without transparency into the server setup behind it,
it's difficult to say more.

Possibly relevant tidbit: www.crisisgroup.org is hosted by
amazonaws.com; it resolves to 34.204.104.28 and 34.195.245.170 for me,
ec2-34-204-104-28.compute-1.amazonaws.com and
ec2-34-195-245-170.compute-1.amazonaws.com.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                address@hidden
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B