Re: missing files because versioning? - Mailing list pgsql-www

From Jonathan S. Katz
Subject Re: missing files because versioning?
Date
Msg-id 63d0fe7c-eb8b-50ab-3268-78c52ab0c1d5@postgresql.org
Whole thread Raw
In response to missing files because versioning?  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: missing files because versioning?
List pgsql-www
On 3/8/23 2:08 PM, Alvaro Herrera wrote:
> Hi
> 
> I just noticed that opening www.postgresql.org under Chromium's DevTools
> mode shows these three errors in the console:
> 
> DevTools failed to load source map: Could not load content for https://www.postgresql.org/media/js/popper.min.js.map:
HTTPerror: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
 
> DevTools failed to load source map: Could not load content for
https://www.postgresql.org/media/css/bootstrap.min.css.map:HTTP error: status code 404,
net::ERR_HTTP_RESPONSE_CODE_FAILURE
> DevTools failed to load source map: Could not load content for
https://www.postgresql.org/media/js/bootstrap.min.js.map:HTTP error: status code 404,
net::ERR_HTTP_RESPONSE_CODE_FAILURE
> 
> It appears that we do have these files under /media/, but with version
> numbers embedded in their names.  Does this mean that we're missing a
> symlink, or perhaps a redirect rule?

These are used for debugging and the errors only show up if you load the 
console. We can silence the error that removes the line that tries to 
load the map files, or you can disable it in your local console i.e. 
uncheck "enable source map files".

I have a patch ready that disables the actual load -- if you see an 
unnecessary amount of 404 traffic to the web servers, I say we just do that.

Jonathan

Attachment

pgsql-www by date:

Previous
From: Alvaro Herrera
Date:
Subject: missing files because versioning?
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: updates for spi / donations info