-
Notifications
You must be signed in to change notification settings - Fork 16
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
Behaviour of the /submit/
endpoint
#22
Comments
Do you think stripping the /wip/ will work reliably? |
I reckon it will not be more unreliable than it was with current On the one hand bluntly ignoring errors is not an ideal approach, on the other hand waiting up to 3-5 minutes on each call is also not an option for many use cases. Maybe it makes sense to introduce some kind of |
You have any idea on how we could implement this in the Python? |
Behaviour of
https://archive.md/submit/
endpoint has changed recently. Now it returns WIP page inRefresh
header (https://archive.md/wip/Z6uhm
) which contains page capture progress and expects client to retry until the page is captured and proper memento URL (https://archive.md/Z6uhm
) returned viaLocation
. This wayarchiveis.capture()
always returns URL of the WIP page.This can be fixed either by retrying until proper URL is available (and somehow handling errors if it is not) or just stripping
/wip/
from URL and hoping for the best.The text was updated successfully, but these errors were encountered: