search

jenkins-infra / helpdesk

Open your Infrastructure related issues here for the Jenkins project
https://github.com/jenkins-infra/helpdesk/issues/new/choose
17 stars 10 forks source link

LF status page redirect may be cached for too long #3660

Open daniel-beck opened 1 year ago

daniel-beck commented 1 year ago

Service(s)

Jira

Summary

A user reports the following behavior they encounter today (redacted):

When I try to view SECURITY-ABC or SECURITY-DEF, it redirects to https://status.linuxfoundation.org/ But SECURITY-GHI and SECURITY-JKL I can access fine.

The redirect set up during maintenance should be reviewed for HTTP 301 mis-use, long cache expiration, and similar.

Reproduction steps

No response

MarkEWaite commented 1 year ago

I had similar redirect issues on the day of the upgrade and had to clear my browsing history for that period. The issue was in my web browser, not in anything that could be adjusted at the Linux Foundation.

I was able to open pages like SECURITY-ABC or SECURITY-DEF, from an incognito browser window on the same computer, but could not open them from my usual browser configuration until I cleared my browsing history. As far as I could tell at that time, it was an issue specific to my web browser or one of the extensions installed in my web browser.

MarkEWaite commented 1 year ago

@daniel-beck can you ask the original reporter of the issue to check with incognito mode as confirmation that it is local to their browser and environment?

daniel-beck commented 1 year ago

I asked them to clear the browser cache, no response yet.

The point is, the status page redirect should not be cached for so long in the first place.

MarkEWaite commented 1 year ago

The point is, the status page redirect should not be cached for so long in the first place.

I'm not sure that is something they can fix. I think that it is the browser choosing to cache the status page, not the web server. when I access those pages, the web server provides the correct page. Is there something that leads you to believe it is the web server providing incorrect data to the browser?

daniel-beck commented 1 year ago

I don't know how the redirect was set up, but I provide two suggestions to check for in the original issue description: Use of HTTP 301, or cache-related headers.

MarkEWaite commented 1 year ago

I'll forward the request to them and ask that they review the configuration they used. Thanks