4 ms·
> Just today, Azure's support system can't handle (among many things) the outlandish characters of "<" or ">". Which is great fun, since it's not like anyone wo
by zinekeller 6y ago
> Just today, Azure's support system can't handle (among many things) the outlandish characters of "<" or ">". Which is great fun, since it's not like anyone would file a highly-technical support request with Azure… right?
Someone in Azure is definitely using the Windows reserved characters for filenames.
- jannes 6y agoReminds me of the fact that filenames in OneDrive are even more restrictive because of some legacy SharePoint software that was representing filenames in URLs. "?" and "#" were not allowed in OneDrive for Business for a long time because they have a special meaning in URLs: https://techcommunity.microsoft.com/t5/microsoft-sharepoint-blog/new-support-for-and-in-sharepoint-online-and-onedrive-for/ba-p/60357 https://techcommunity.microsoft.com/t5/microsoft-sharepoint-... The Rclone documentation has a full list of problematic OneDrive characters: https://rclone.org/onedrive/#restricted-filename-characters https://rclone.org/onedrive/#restricted-filename-characters
- CodesInChaos 6y agoI think misguided XSS protection is the most likely culprit here.