Closed larserikfagernaes closed 9 years ago
It means the request was badly formed, probably due to either malformed JSON or potentially the token used when sending the request. It might have to do with the logging in request. When do you receive the error?
Hmm, i get the error when logging in. Here is more of the error message: File "build/bdist.macosx-10.9-intel/egg/pysnap/utils.py", line 88, in request File "/Library/Python/2.7/site-packages/requests-2.5.3-py2.7.egg/requests/models.py", line 831, in raise_for_status raise HTTPError(http_error_msg, response=self) The bot was working before, i dont know what happend.
The error is occurring when sending the request, this doesn't really help. Does it occur when the log in request is sent?
i belive so, but im not too good at programming, here is the whole error so you can see for yourself:
/System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 /Users/larserik/PycharmProjects/Koding/init.py
[2015-03-13 12:27:45,045] Starting new HTTPS connection (1): feelinsonice-hrd.appspot.com
[2015-03-13 12:27:45,339] "POST /bq/login HTTP/1.1" 400 None
Traceback (most recent call last):
File "/Users/larserik/PycharmProjects/Koding/init.py", line 41, in
File "build/bdist.macosx-10.9-intel/egg/pysnap/init.py", line 83, in _request
File "build/bdist.macosx-10.9-intel/egg/pysnap/utils.py", line 88, in request File "/Library/Python/2.7/site-packages/requests-2.5.3-py2.7.egg/requests/models.py", line 831, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 400 Client Error: Bad Request requests.exceptions.HTTPError: 400 Client Error: Bad Request
i also get this error:
[2015-03-13 13:38:43,461] Starting new HTTPS connection (1): feelinsonice-hrd.appspot.com
[2015-03-13 13:38:44,573] "POST /loq/login HTTP/1.1" 403 434
Traceback (most recent call last):
File "/Users/larserik/Desktop/PycharmProjects/untitled/NTNUsnap-master/nfp.py", line 78, in
i think i solved it my going through proxies.
Yeah, your IP was probably banned, not much to do from the library's side, except maybe better error reporting :)
larserikfagernaes Can you please share the details what exactly you did to solve this from proxies side?
I keep on getting this error, anny idea what it is?