On Sun, Aug 28, 2022 at 12:09:51AM +0200, Ángel wrote: > On 2022-08-27 at 20:32 +0200, tomas@tuxteam.de wrote: > > On Sat, Aug 27, 2022 at 12:28:38PM -0600, tony mollica wrote: > > > Yes, no problems accessing the .asp pages with Debian 10 and > > > chrome. Both 10 and 11 have the latest Chrome version. I'm not > > > seeing any version change notes for Chrome or Debian 11 that appear > > > to affect this .asp behavior. Not to say I haven't missed > > > something. > > > > Hm. As I said -- the .asp shouldn't be the problem. I don't know > > Chrome very well (I try to avoid it), so I fear I can't help. Perhaps > > there is a debugging mode to see exactly what request is receiving > > the 404 answer. Then compare with the functioning version. > > > > A 404 is definitely server-side (unless Chrome is lying to you). > > > > Cheers > > In Chromium you can use Ctrl+Shit+I to open the developer tools, where > you have a Network tab where requests and responses can be seen. > > Tony, as Tomas noted, the error will be provided by the router itself, > not the browser. The router might be doing something strange, such as > returning different responses based on the User Agent, or it loses > track that the user is logged in, and in that case it shows a 404... ...or it generates a link to some local (the user's computer) resource (which then would exist in the old installation but not in the new) or something like that. Web is like that. It's dystopia let loose ;-) Cheers -- t
Attachment:
signature.asc
Description: PGP signature