You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Are you sure? What if you enable connection_verbose(true), and enable trace level logs? You can see all the bytes on the connection. I'm not able to reproduce, myself.
Let me illustrate this with an example:
If I request this URL:
https://www.woodlandtrust.org.uk/media/31398/white-willow-twig-with-leaves-in-summer-alamy-b3b978-wildlife-gmbh.jpg?center=0.5074626865671642,0.46218487394957986&mode=crop&heightratio=0.5622047244094488188976377953&width=647&rnd=132102663080000000
The the response is a
302 Found
with the following headers:Requesting the Location URL we get the headers:
However, doing
request::get
on the first URL produces aResponse
with the body of the second, but withContent-Type: text/html
.This seems wrong and I can't find a way to access the correct header of
image/jpeg
.Am I missing something?
The text was updated successfully, but these errors were encountered: