Hey!
We at Arquivo.pt updated our Pywb, and in consequence the announcing URL for a resource TimeMap changed.
We see that the TimeTravel Service agent is hitting our servers for timemaps on an URL like this:
https://arquivo.pt/wayback/timemap/*/https://fccn.pt
But instead of using that URL it should be getting the timemaps from https://arquivo.pt/wayback/timemap/link/https://fccn.pt.
We added a redirect so the TimeTravel requests don't hit the wall.
We would like to understand better the implications of this change and that TimeTravel service stops going through the redirect.
Should not time travel service following the announced timemap?
Have we done something wrong at our side?
Best regards!
--
---
You received this message because you are subscribed to the Google Groups "Memento Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to memento-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/c9d84d7a-beb2-4ceb-8c84-8c60c11dd7fb%40googlegroups.com.
On Mon, Nov 18, 2019 at 4:59 AM Daniel Bicho <danie...@gmail.com> wrote:
--Hey!
We at Arquivo.pt updated our Pywb, and in consequence the announcing URL for a resource TimeMap changed.
We see that the TimeTravel Service agent is hitting our servers for timemaps on an URL like this:https://arquivo.pt/wayback/timemap/*/https://fccn.pt
But instead of using that URL it should be getting the timemaps from https://arquivo.pt/wayback/timemap/link/https://fccn.pt.
We added a redirect so the TimeTravel requests don't hit the wall.
We would like to understand better the implications of this change and that TimeTravel service stops going through the redirect.
Should not time travel service following the announced timemap?
Have we done something wrong at our side?
Best regards!
---
You received this message because you are subscribed to the Google Groups "Memento Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to memen...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to memento-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/6b4ec372-cebe-4c24-9fcf-41e17f9d4993%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/CANAUx6je21sQKxgH_01tSKS5bce8Uw2imryebRWwS%3DLyfV5Rkg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/CANAUx6je21sQKxgH_01tSKS5bce8Uw2imryebRWwS%3DLyfV5Rkg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/6b4ec372-cebe-4c24-9fcf-41e17f9d4993%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to memento-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/6b4ec372-cebe-4c24-9fcf-41e17f9d4993%40googlegroups.com.
Hi Daniel,I just noticed that I never answered your question:No, no TimeMap-consuming client (not only the TimeTravel service) can handle these timemaps as they are non-compliant with the Memento specification. IMHO, building a temporary workaround is not a good solution as it opens the door to having to accommodate many more bad implementations and that means the end of interoperability. So the bottom line is this needs to be addressed in pywb (as I think Ilya acknowledged), there is no other solution.cheersM
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/6b4ec372-cebe-4c24-9fcf-41e17f9d4993%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to memento-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/memento-dev/8ddab29e-3b54-4a4e-9331-4e15cf6e82cc%40googlegroups.com.