If two separate websites are both using imageproxy for images, then it turns out that nesting these URLs fails due to the way the URL parsing works.
For example, a website publishes an image URL in a feed such as
https://img.example.net/w_960,c_fill/https://media.example.net/3def0f60f.jpg
Then a feed reader finds that image URL and serves it up from its own imageproxy, creating a URL like
https://images.reader.example/1240x0/https://img.example.net/w_960,c_fill/https://media.example.net/3def0f60f.jpg
This fails because it's unable to recognize where the parameters from the first imageproxy end and the next one start.
If two separate websites are both using imageproxy for images, then it turns out that nesting these URLs fails due to the way the URL parsing works.
For example, a website publishes an image URL in a feed such as
Then a feed reader finds that image URL and serves it up from its own imageproxy, creating a URL like
This fails because it's unable to recognize where the parameters from the first imageproxy end and the next one start.