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

pywb returns status code 200 when archive url not found #45

Closed
GilHoggarth opened this issue Aug 9, 2019 · 3 comments
Closed

pywb returns status code 200 when archive url not found #45

GilHoggarth opened this issue Aug 9, 2019 · 3 comments

Comments

@GilHoggarth
Copy link

For example, https://webarchive.org.uk/wayback/archive/2019/www.coinbase.com
In the wa-www nginx log, this request is recorded as a status code 200 whereas the on-screen message is "Url Not Found
The url http://www.coinbase.com/ could not be found in this collection. ".

@ikreymer
Copy link
Contributor

ikreymer commented Nov 1, 2019

The inner frame response, https://www.webarchive.org.uk/wayback/archive/2019mp_/http://www.coinbase.com/ is a 404, but not the outer frame, which is always a 200.
The reason is that the lookup does not happen until the inner frame is loaded, to avoid a double query and load the outer frame quickly, but maybe there's a way to improve this..

@anjackson
Copy link
Contributor

Related somewhat to #44. Note that the TimeGate URL (https://beta.webarchive.org.uk/wayback/archive/http://www.coinbase.com/) does the right thing.

@anjackson
Copy link
Contributor

I'm going to call this ticket a duplicate of #44, having clarified that this is part of that issue.

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

3 participants