We are using [url removed, login to view] to read redirects and store for later use. I attached a small java example that shows how we input an uri and then find the final redirect address by detecting 301 or 302 responses and reading the location header.
We have a problem for some sites, where we cannot decode the location header correctly. Headers are supposed to be ascii only but for some servers it is not the case.
In the attached code there are an example where location ends up with a garbage response due to decoding issues.
For example, following the redirect [url removed, login to view] which goes to [url removed, login to view]¥ôäÄÄÈÀÔÀÀÀÀÀÀ7p
So basically the task is to solve this problem, either by implementing a RedirectStrategy for the htpclient or another suitable approach
13 freelancers are bidding on average $434 for this job
Hello, I am a httpclient expert,I have used http3&4 for 4 years I can implement a customized RedirectStrategy to fix this problem please let me hellp you Bing