-
Notifications
You must be signed in to change notification settings - Fork 34
return HTTP/1.1 400 Bad Request #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Which message do you get back from the API? |
The token can't not write to token file.
The problem seems use But dump $result still empty. I try to solveing........ |
I'm facing also the same @dowdot catch it, but Note that we can achive that later result without setting Many many thanks. |
I use curl exec is ok , but use api-clients call will return HTTP/1.1 400 Bad Request error...
who can help me....
[root@weather IPAM]# curl -X GET http://ipam.xxx.xxx.xxx/api/ipam/user/ --header 'token:h==kas7bR$eX__2TgHKyW0oO'
{"code":200,"success":true,"data":{"expires":"2018-04-14 20:24:39"},"time":0.043}
The text was updated successfully, but these errors were encountered: