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: 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/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.
By definition it's unnecessary given we don't use it :-) it's not much traffic on the server side though, but it certainly seems like something worth optimizing for client side improvements if it's easy enough to do. At least unless it turns out to be ugly or invasive against something else.
So it sounds like completing that patch is worthwhile.