Inconsistencies in what the browser gets and curl gets

Return is a JSON string but I use Curl-l http://.... But can't get

Return

404 Not Found
404 Not Found
The requested URL /mauth/usr/exists was not found on this server.

Reply content:

Return is a JSON string but I use Curl-l http://.... But can't get

Return

404 Not Found
404 Not Found
The requested URL /mauth/usr/exists was not found on this server.

The problem later found that the network link problem, the implementation of curl that host and target server is isolated, can not access each other, egg pain!

User-agent, Cookies, Accept, referer and other parameters all affect the request result.

I usually first use fiddler to find the minimum required parameters and cookies, and then curl.

, the latest version of Chrome's JavaScript debugging tool already supports Curl replication (which can fully simulate browser access, including Header,cookie, operating system information, etc.), by first knocking down the network and then accessing this page Then right-click on the list and have a copy as curl. And then straight curl worked.

The URL is wrong to write ... or a service-side limit on user-agent ...

Use a mock-up of –user-agent other browsers to see ...

