When curl is applied to obtain the address, BadRequest is displayed. However, this address can be opened in the browser.

When curl is used to obtain the address, BadRequest is displayed. however, this address can be opened in the browser and displayed as BadRequest when curl is used to obtain the address. but this address can be opened in the browser, and the program is OK. You can collect other URLs in several cases. remote clients can detect client-side Filtering. 2. remote redir behavior 3. request intermediate layer 4. when curl is used to obtain the IP address, Bad Request is displayed. however, this address can be opened in the browser.
When curl is used to obtain the address, the Bad Request is displayed. However, this address can be opened in the browser, and the program is OK. Other websites can be collected.

------ Solution --------------------
Situations
1. remote clients have detected client filtering behavior
2. redir behavior on the remote end
3. request intermediate layer
4. filtering behavior in the near-end
5. a process has a cache mechanism.
6. unknown

In some cases, you are not directly connected to "real content"

There is no ultimate solution. if there is one, you can make fun of a principal.


------ Solution --------------------
I have encountered this situation, that is, I have not obtained the real address!
You can try the firefox plug-in httpfox to see if you can get the real address. if not
You can download a software to obtain the real address.