Hello.
Site works fine here (Firefox 128.0)
On 7/18/24 14:24, Roger Price wrote:
On Thu, 18 Jul 2024, Greg Wooledge wrote:
On Thu, Jul 18, 2024 at 02:27:39 -0400, Felix Miata wrote:
Russell L. Harris composed on 2024-07-18 06:06 (UTC):
Would someone kindly verify that chewy.com is accessible?
https://www.chewy.com/ looks normal from FL in Chromium:
Works for me in Google Chrome.
ping www.chewy.com replies: 64 bytes from
g2a02-26f0-2b00-06a2-0000-0000-0000-0c35.deploy.static.akamaitechnologies.com
(2a02:26f0:2b00:6a2::c35): icmp_seq=1 ttl=49 time=18.8 ms
Lynx replies: waiting for response.
w3m replies: Waiting for reply...
W3C validator replies: 429 Too Many Requests
curl --head replies: HTTP/2 429
content-type: text/html; charset=utf-8
x-kpsdk-ct: 0r17x8iBB9ocm6h...
access-control-expose-headers: x-kpsdk-ct,x-kpsdk-r,x-kpsdk-c ...
The access-control-expose-headers looks like unneeded complexity by
chewy. Even Microsoft doesn't do it.
Roger
