web site displays blank page

[Russell L. Harris]

When I try to visit www.chewy.com a blank page. This is a major pet
supply web site. Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.

I have tried two different computers and both Firefox and Chromium. I
updated Debian-12. I emptied the browser cache. No change.

A week or two ago, chewy.com displayed perfectly.

My ISP is RTA. I am in a rural area near Austinn, Texas, and have a
10/1 microwave link. Could the problem be with RTA?

Would someone kindly verify that chewy.com is accessible?

RLH

[Felix Miata]

Post by Russell L. Harris
When I try to visit www.chewy.com a blank page. This is a major pet
supply web site. Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium. I
updated Debian-12. I emptied the browser cache. No change.
A week or two ago, chewy.com displayed perfectly.
My ISP is RTA. I am in a rural area near Austinn, Texas, and have a
10/1 microwave link. Could the problem be with RTA?
Would someone kindly verify that chewy.com is accessible?

https://www.chewy.com/ looks normal from FL in Chromium:
[copied/pasted]
High-quality, great value from brands by Chewy
American Journey Peanut Butter Recipe Grain-Free Oven Baked Crunchy Biscuit Dog
Treats, 16-oz bag, bundle of 2
American Journey Peanut Butter Recipe Grain-Free Oven Baked Crunchy Biscuit Dog
Treats, 16-oz bag, bundle of 2
By
Rated 4.5 out of 5 stars
4.5
4,775
$12.60Chewy Price
$12.98
[/]

[Greg Wooledge]

Post by Russell L. Harris
Would someone kindly verify that chewy.com is accessible?

Works for me in Google Chrome.

[Roger Price]

Post by Greg Wooledge

Post by Russell L. Harris
Would someone kindly verify that chewy.com is accessible?

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

[mindaugas]

Hello.

Site works fine here (Firefox 128.0)

Post by Roger Price

Post by Greg Wooledge

Post by Russell L. Harris
Would someone kindly verify that chewy.com is accessible?

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

[David]

On Thu, 2024-07-18 at 06:06 +0000, Russell L. Harris wrote:

Hullo Russell,

When I try to visit www.chewy.com a blank page.  This is a major pet
supply web site.  Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium. 
I
updated Debian-12.  I emptied the browser cache.  No change.
A week or two ago, chewy.com displayed perfectly.
My ISP is RTA.  I am in a rural area near Austinn, Texas, and have a
10/1 microwave link.  Could the problem be with RTA?
Would someone kindly verify that chewy.com is accessible?

Blank page with Chromium, but accessible via Firefox, on SID, over
Starlink.
Cross browser compatibility design issue?
Cheers!

RLH

[Russell L. Harris]

Post by David
Blank page with Chromium, but accessible via Firefox, on SID, over
Starlink.
Cross browser compatibility design issue?
Cheers!

The blank page you get with Chromium makes me less concerned with RTA,
though there are other issues with RTA.

What I don't understand is that I never recall encountering this
problem before, and I have been using the CHEWY website for years.

If a change made by CHEWY caused the problem, they should know within
a day. Or perhaps everyone but I has switched from a computer to a
smartphone.

Thanks for the reports.

RLH

[Alain D D Williams]

Post by Russell L. Harris
When I try to visit www.chewy.com a blank page. This is a major pet
supply web site. Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium. I
updated Debian-12. I emptied the browser cache. No change.
A week or two ago, chewy.com displayed perfectly.
My ISP is RTA. I am in a rural area near Austinn, Texas, and have a
10/1 microwave link. Could the problem be with RTA?
Would someone kindly verify that chewy.com is accessible?

HTTP code 429 means "Too Many Requests (RFC 6585)"

$ curl --head https://www.chewy.com/
HTTP/2 429
content-type: text/html; charset=utf-8
x-kpsdk-ct: 03Vhg1rHHEmv7VMgvAv2tLEGyrlWwedwtTXLLwhV37Jqel51VNOL8UHcFw5fHbuRuG2METLn8zJJb148AhDbEh1FSN7hCRLDWawPK8L1uHJj8A9JeCMSXTtSIy90qNGEuT0trYKzEveuIVapXLCtN0TwqGJbR7ZMKBQX1ix0o7j6tvAI21Fous
access-control-expose-headers: x-kpsdk-ct,x-kpsdk-r,x-kpsdk-c
p3p: CP="This site does not specify a policy in the P3P header"
expires: Thu, 18 Jul 2024 06:12:55 GMT
cache-control: max-age=0, no-cache, no-store
pragma: no-cache
date: Thu, 18 Jul 2024 06:12:55 GMT
set-cookie: KP_UIDz-ssn=03Vhg1rHHEmv7VMgvAv2tLEGyrlWwedwtTXLLwhV37Jqel51VNOL8UHcFw5fHbuRuG2METLn8zJJb148AhDbEh1FSN7hCRLDWawPK8L1uHJj8A9JeCMSXTtSIy90qNGEuT0trYKzEveuIVapXLCtN0TwqGJbR7ZMKBQX1ix0o7j6tvAI21Fous; Max-Age=86400; Path=/; Expires=Fri, 19 Jul 2024 06:12:55 GMT; HttpOnly; Secure; SameSite=None
set-cookie: KP_UIDz=03Vhg1rHHEmv7VMgvAv2tLEGyrlWwedwtTXLLwhV37Jqel51VNOL8UHcFw5fHbuRuG2METLn8zJJb148AhDbEh1FSN7hCRLDWawPK8L1uHJj8A9JeCMSXTtSIy90qNGEuT0trYKzEveuIVapXLCtN0TwqGJbR7ZMKBQX1ix0o7j6tvAI21Fous; Max-Age=86400; Path=/; Expires=Fri, 19 Jul 2024 06:12:55 GMT; HttpOnly
set-cookie: device-id=366803eb-cfb8-4564-8805-770df06107bc; expires=Wed, 09-Jul-2025 06:12:55 GMT; path=/; domain=.chewy.com; secure
alt-svc: h3=":443"; ma=93600
x-content-type-options: nosniff
strict-transport-security: max-age=86400 ; preload
edge-cache-tag: homepage-not-loggedin
x-request-id: 35f11fa
set-cookie: akavpau_defaultvp=1721283475~id=cd67f1b621214ab4606205c4eaec74e4; Path=/; HttpOnly; Secure; SameSite=None
set-cookie: akaalb_chewy_ALB=1721283775~op=prd_kasada:prd-kasada-haproxy-use2|~rv=39~m=prd-kasada-haproxy-use2:0|~os=43a06daff4514d805d02d3b6b5e79808~id=498bb70aac1e50701a980f57c3e5b82a; path=/; Expires=Thu, 18 Jul 2024 06:22:55 GMT; HttpOnly; Secure; SameSite=None
akamai-grn: 0.24f61002.1721283175.35f11fa
set-cookie: _abck=258D45B94A93D168BD6B94CB00DE2B77~-1~YAAQJPYQAlIoFMKQAQAA/OR4xAx1C/6M1x48v/FrONZhoz10KvKWEQLffLEqHQ4gUg9CJeYvBx9F4HKbn/oYVXqRWU8By+3DnOqZH+T5cEXMwzIZm4T+qm+SGM21/9et+X2dEp/qCXRxxFEapLDzoUo4Z+toWuIOHy+5Tlfdy/5qxyawc/UsoqIE8N0q+Bt44wmGLWEU7E/GB6X0om3nj2ZW/+eXdmw+dXA7HTKOQOZvPgirfx9KUXTE8rCvg8U59qRm0mssp5KVg3dkFO+RQKb4GBk05hLorC9/r2ab9pWjd++jwTW6DxvIUpmKW9P9dgHOjojFoJbnsVR2Sap65GvGeqFQzKKhyHKZuDSDLIhA6l1/Av1X9w==~-1~-1~-1; Domain=.chewy.com; Path=/; Expires=Fri, 18 Jul 2025 06:12:55 GMT; Max-Age=31536000; Secure
set-cookie: bm_sz=303CEEFC20F8A4A1A27DCF68B25ED773~YAAQJPYQAlMoFMKQAQAA/OR4xBiVVtG8Gq9Jf1J1QX/rZ8vNzdMTBCTK0BboTlg+6Qu5nWA6Lxh7P0LonjJWnz6BPEIvPuQkDTnJTtW+gIbC3Jj8Hy6UjA5/uUQ71EyRMYBaw17wN4BQn7l3l7+xuSGmgVuZhVv9pngUmZH+vTLZhD7R5+g55IImAU7G5p3kAn/zLEvhVPoNu9WCra/s2Zxhrcib2CXHmU5vLsKJBCwZiA2lpJKpzTM+dSp1ZlN9XSfY0j7nhLZXC8OmYGuI8R4mRCZRKs2T2d/iUdXO6CdjL5BzXS8WSfEq5YoXlN9zxXNR+9ujPrUhSHVRU5O04pcDTAXtUs/xUkCVaPXJxj8yid37dP6Ngrvt2xsBVGPHHw==~3159105~3420471; Domain=.chewy.com; Path=/; Expires=Thu, 18 Jul 2024 10:12:55 GMT; Max-Age=14400
server-timing: ak_p; desc="1721283175160_34666020_56562170_23218_76689_28_206_15";dur=1

[Richard Owlett]

Post by Alain D D Williams

Post by Russell L. Harris
When I try to visit www.chewy.com a blank page. This is a major pet
supply web site. Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium. I
updated Debian-12. I emptied the browser cache. No change.
A week or two ago, chewy.com displayed perfectly.
My ISP is RTA. I am in a rural area near Austinn, Texas, and have a
10/1 microwave link. Could the problem be with RTA?
Would someone kindly verify that chewy.com is accessible?

HTTP code 429 means "Too Many Requests (RFC 6585)"
$ curl --head https://www.chewy.com/
HTTP/2 429
content-type: text/html; charset=utf-8

[ *SNIP* what I couldn't understand ]

SeaMonkey 2.49.4 on Debian 9.13 *CAN* display that page.
[establishes that old vs new client side software in not the issue]

HOWEVER I can duplicate your symptom.
Due to personal needs/preferences I surf with many disabled options
[including JavaScript and cookies].

My test procedure was:
Opened https://www.chewy.com/ .
I got a blank page and SeaMonkey's status line said "Done"
Closed window.
Enabled JavaScript.
Opened https://www.chewy.com/ .
I got a blank page with sets of "transferring data"/"Done" messages
SeaMonkey's status line then said "Done"
The screen remained blank with mouse cursor indicating activity.

Post by Alain D D Williams
A script on this page may be busy, or it may have stopped

responding.

Post by Alain D D Williams
You can stop the script now, open the script in the debugger, or let
the script continue.

https://www.chewy.com/149e9513…TQ5N2EtYTYyNC0wNTMxZjg5NjJkZjI:27
I opened the debugger and got a tool I don't know how to use. It was
apparent that it gave enough information that a knowledgeable user
could diagnose the exact failure mode.
Closed window.
Enabled JavaScript *and* cookies
Opened https://www.chewy.com/ .
I got a perfectly normal page.

I'm assuming the "Unresponsive script" box is SeaMonkey's response to a
"HTTP code 429".

Hope this helps.

[e***@gmx.us]

Post by Richard Owlett

Post by Alain D D Williams

When I try to visit www.chewy.com a blank page.  This is a major pet
supply web site.  Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium.  I
updated Debian-12.  I emptied the browser cache.  No change.
A week or two ago, chewy.com displayed perfectly.
My ISP is RTA.  I am in a rural area near Austinn, Texas, and have a
10/1 microwave link.  Could the problem be with RTA?
Would someone kindly verify that chewy.com is accessible?

HTTP code 429 means "Too Many Requests (RFC 6585)"
$ curl --head https://www.chewy.com/
HTTP/2 429

HOWEVER I can duplicate your symptom.
Due to personal needs/preferences I surf with many disabled options
[including JavaScript and cookies].

Good point. Further testing was indeed warranted.

If I enables JS for appsflyer.com I get a warning about DRM-protected media.
So maybe your version of Firefox _thinks_ it can handle DRM, but really can't?

--
Are you confident that you appear to be professional in your electronic
communication? Consider this: A: No
Q: Can I top post? from ***@xx.co.uk

[Richard Owlett]

Post by Richard Owlett

Post by Alain D D Williams

When I try to visit www.chewy.com a blank page.  This is a major pet
supply web site.  Other web sites display as usual without problems.
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium.  I
updated Debian-12.  I emptied the browser cache.  No change.
A week or two ago, chewy.com displayed perfectly.
My ISP is RTA.  I am in a rural area near Austinn, Texas, and have a
10/1 microwave link.  Could the problem be with RTA?
Would someone kindly verify that chewy.com is accessible?

HTTP code 429 means "Too Many Requests (RFC 6585)"
$ curl --head https://www.chewy.com/
HTTP/2 429

HOWEVER I can duplicate your symptom.
Due to personal needs/preferences I surf with many disabled options
[including JavaScript and cookies].

Good point.  Further testing was indeed warranted.
If I enables JS for appsflyer.com I get a warning about DRM-protected media.
 So maybe your version of Firefox _thinks_ it can handle DRM, but
really can't?

You snipped too much ;{
I don't use ANY version of Firefox.
I use SeaMonkey 2.49.4 on Debian 9.13 .
They have a common ancestor - Netscape Navigator.
For appsflyer.com with JavaScript *AND* cookies disabled, I see an
apparently normal page and clicking any URL works.
I suspect that enabling JavaScript would allow what I suspect to be
drop-down menus [e.g "Kickstart app growth" etc.] to work.
Due to security concerns, I will NOT enable either JavaScript or cookies
for for an unknown site marketing software. [dating back to days of
vacuum tube CPUs I'm naturally suspicious ;]

[e***@gmx.us]

My ISP is RTA.  I am in a rural area near Austinn, Texas, and have a > 10/1 microwave link.  Could the problem be with RTA?

It's probably a routing issue between you and them. Or maybe "delivery
content network" (That's what it's called, right? A company with fat pipes
in several places that rents out their bandwidth.) got temporarily
misconfigured. their I've had instances where one or more sites become
inaccessible for minutes or hours, then work again.

Would someone kindly verify that chewy.com is accessible?

Works. With JS off it looks the same, but none of the menus work.

--
6 x 9 = 42
13
--DNA (paraphrased)

[Richard Owlett]

Post by e***@gmx.us

My ISP is RTA.  I am in a rural area near Austinn, Texas, and have a >
10/1 microwave link.  Could the problem be with RTA?

It's probably a routing issue between you and them. Or maybe "delivery
content network" (That's what it's called, right?  A company with fat pipes
in several places that rents out their bandwidth.) got temporarily
misconfigured.  their I've had instances where one or more sites become
inaccessible for minutes or hours, then work again.

Would someone kindly verify that chewy.com is accessible?

Works.  With JS off it looks the same, but none of the menus work.

Using SeaMonkey 2.49.4 on Debian 9.13 [also see my response to Alain]
With JS off but cookies enabled I see 11 cookies and blank page.
With JS on and cookies enabled I see 16 cookies and normal page.

[Dan Ritter]

Post by e***@gmx.us

My ISP is RTA.  I am in a rural area near Austinn, Texas, and have a > 10/1 microwave link.  Could the problem be with RTA?

It's probably a routing issue between you and them. Or maybe "delivery
content network" (That's what it's called, right? A company with fat pipes
in several places that rents out their bandwidth.) got temporarily
misconfigured. their I've had instances where one or more sites become
inaccessible for minutes or hours, then work again.

Content delivery network -- in this case, Akamai, which I used
to work for 20 years ago.

The 429 error indicates either that the local node is
overwhelmed (unlikely) or that the client has asked for a limit
on traffic to prevent a giant bill.

-dsr-

[Jeffrey Walton]

Post by Dan Ritter

Post by e***@gmx.us

My ISP is RTA. I am in a rural area near Austinn, Texas, and have a > 10/1 microwave link. Could the problem be with RTA?

It's probably a routing issue between you and them. Or maybe "delivery
content network" (That's what it's called, right? A company with fat pipes
in several places that rents out their bandwidth.) got temporarily
misconfigured. their I've had instances where one or more sites become
inaccessible for minutes or hours, then work again.

Content delivery network -- in this case, Akamai, which I used
to work for 20 years ago.
The 429 error indicates either that the local node is
overwhelmed (unlikely) or that the client has asked for a limit
on traffic to prevent a giant bill.

I think the company is currently in a downward spiral. Saving money
sounds like a plausible reason for the problems with its website.
Confer, <https://techcrunch.com/2023/11/14/online-pet-goods-retailer-chewy-lays-off-200-employees/>.

Jeff

[Russell L. Harris]

Post by e***@gmx.us

My ISP is RTA.?? I am in a rural area near Austin, Texas, and have a
10/1 microwave link.?? Could the problem be with RTA?

It's probably a routing issue between you and them. Or maybe "delivery
content network" (That's what it's called, right? A company with fat pipes
in several places that rents out their bandwidth.) got temporarily
misconfigured. their I've had instances where one or more sites become
inaccessible for minutes or hours, then work again.

CHEWY is a large nation-wide outfit. I suspect the trouble is with
RTA, because of frequent freezes when viewing a certain news website,
while all other streams are uninterrupted with my 10/1 service from
RTA.

I just installed Konqueror and rebooted my firewall (ipFire), but I
still get a blank page for CHEWY.COM.

What should I try next?

RLH

[Max Nikulin]

CHEWY is a large nation-wide outfit.  I suspect the trouble is with
RTA, because of frequent freezes when viewing a certain news website,
while all other streams are uninterrupted with my 10/1 service from
RTA.

Some web sites are rather aggressive with their protection against DDoS
and content scraping. Wget, curl, browsers blocking cookies and
JavaScript may easily be banned. If you are unlucky, whole subnet of
your provider may be temporary blocked. I have not tried if it is
applied to the particular site.

[c***@surfnaked.ca]

Post by Russell L. Harris
When I try to visit www.chewy.com a blank page. This is a major

pet

Post by Russell L. Harris
supply web site. Other web sites display as usual without

problems.

Post by Russell L. Harris
I phoned CHEWY and they say their system is on-line.
I have tried two different computers and both Firefox and Chromium.

I

Post by Russell L. Harris
updated Debian-12. I emptied the browser cache. No change.

I tried accessing it with my main browser, Seamonkey 2.53.18.2.
The page briefly displayed, then blanked out. Firefox 115.7.0esr
displayed the page properly. Oddly enough, I tried Seamonkey again
and it worked. My copy of Seamonkey is using NoScript 5.1.9,
which I often have to disable to display web pages.

For what it's worth, I entered http://www.chewy.com on the address
bar. On all subsequent attempts, this gets changed to https:.

I'm having this problem on an increasing number of web sites;
I suspect that web page building tools are becoming more and
more hostile toward any browsers except for the anointed few
(Edge and Chrome, plus Safari for the Mac folks).

--
/~\ Charlie Gibbs | We'll go down in history as
\ / <***@kltpzyxm.invalid> | the first society that wouldn't
X I'm really at ac.dekanfrus | save itself because it wasn't
/ \ if you read it the right way. | cost-effective. -- Kurt
Vonnegut

[Russell L. Harris]

Post by c***@surfnaked.ca
I'm having this problem on an increasing number of web sites;
I suspect that web page building tools are becoming more and
more hostile toward any browsers except for the anointed few
(Edge and Chrome, plus Safari for the Mac folks).

I once had a W7P machine which helped me check such matters, but
hardware failures on my ancient machines necessitated that I wipe W7P
and install Debian. I need to replace that box.

I finally got hold of a support tech at RTA in Smithville, and found
that www.chewy.com displays properly on a Windows machine at their
Smithville office.

RLH