Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

logging/handling of redirects #115

Open
jbfaden opened this issue Oct 28, 2024 · 1 comment
Open

logging/handling of redirects #115

jbfaden opened this issue Oct 28, 2024 · 1 comment

Comments

@jbfaden
Copy link
Member

jbfaden commented Oct 28, 2024

Larry and I were talking about how redirects are handled, and that 301 (permanent) are not really handled, other than performing the redirect. I was going to start logging these to a file, so that a script could be written to rewrite the .vap or script which is using the old address. It occurred to me that I could just log this at the old position, and then it occurred to me that redirects probably don't work when the resource or Autoplot is off-line. This needs to be studied.

@jbfaden
Copy link
Member Author

jbfaden commented Oct 29, 2024

Presently the FileSystem handling redirects to pick up the file, but the file is cached at the location requested. For example, suppose http://autoplot.org/data/autoplot.cdf is requested. Even though this redirects to https://autoplot.org/data/autoplot.cdf?Magnitude, the data is stored at the old http location.

I propose that the file be kept in the new location, and then the redirect would be kept in the .meta directory. Alternatively, FSCACHE/https/autoplot.org/data/autoplot.cdf.301 could be a file containing the new location.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant