I narrowed it down to those two almost identical image URIs:
Fails:
https://rs.wescover.com/image/upload/f_auto,q_auto/v1/ar08-b
Works:
https://rs.wescover.com/image/upload/f_auto/v1/ar08-b
https://rs.wescover.com/image/upload/q_auto/v1/ar08-b
It’s not about the content of the image “bytes” - it’s the URI itself.
So as you see - the “,” (comma) mark in the URL is that causes the different. Most likely somthing about the data URI generation code fails to parse the comma as a proper part of the URI.
We need to use commas since this is the syntax of our CDN provider - and I believe this is a valid URI character to use. (See RFC3986 “reserved” delimiters).
wdyt?