The cause is that these URLs are generated with both a https:// prefix, and a BASE_URL which also contains a protocol.
What is unclear to me is what happens with the colon after the second https. It seems to get removed somewhere in PDF generation, whereas a colon that correctly defines a hostname:port combination does not.
This mystery shouldn't matter for our fix, though.
Example of a broken link:
https://https//fetc.hum.uu.nl/media/FETC-AK-24-044-01-van_Es-T1-Briefing.docxThe cause is that these URLs are generated with both a
https://prefix, and aBASE_URLwhich also contains a protocol.What is unclear to me is what happens with the colon after the second https. It seems to get removed somewhere in PDF generation, whereas a colon that correctly defines a
hostname:portcombination does not.This mystery shouldn't matter for our fix, though.