This is working for me. Now if a web server decides to strip out the double slash from an archived https URL, the resource will still be served as is done for http. For example, the following URL should now serve correctly instead of giving a Resource Not in Archive (notice the single slash after https:/): http://localhost:8080/wayback/20190411203428/https:/example.com/ . I am including an update to the release notes and a relevant URL in ReplayRequestParserTest. This will close #398 . Thanks for contributing this @peveikko !
This is working for me. Now if a web server decides to strip out the double slash from an archived
httpsURL, the resource will still be served as is done forhttp. For example, the following URL should now serve correctly instead of giving aResource Not in Archive(notice the single slash afterhttps:/): http://localhost:8080/wayback/20190411203428/https:/example.com/ . I am including an update to the release notes and a relevant URL inReplayRequestParserTest. This will close #398 . Thanks for contributing this @peveikko !