I am using AsyncClient, and it looks like, even with referer=False set on the client, a referer header is being sent when following 307 redirects. This is a major problem for my use case and I guess means I'm going to have to implement my own redirect handling logic until this is fixed. It's also rather unusual behavior as web browsers don't usually add a new referer header when following redirects.
I am using AsyncClient, and it looks like, even with referer=False set on the client, a referer header is being sent when following 307 redirects. This is a major problem for my use case and I guess means I'm going to have to implement my own redirect handling logic until this is fixed. It's also rather unusual behavior as web browsers don't usually add a new referer header when following redirects.