We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
o_O
$ curl -vvv http://…@ci.zhdk.ch/cider-ci/api/jobs/?branch-descendants=mfa_master * Trying 195.176.247.161... * Connected to ci.zhdk.ch (195.176.247.161) port 80 (#0) * Server auth using Basic with user 'mfa' > GET /cider-ci/api/jobs/?branch-descendants=mfa_master HTTP/1.1 > Host: ci.zhdk.ch > Authorization: Basic bWZhOk5pdi1haXJ0LWFmdC11cmItT3ctRWRzLXVULUNlLXF1 > User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Trident/5.0) > Accept: */* > Referer: > < HTTP/1.1 200 OK < Date: Tue, 24 Nov 2015 00:05:08 GMT < Server: Jetty(9.2.10.v20150310) < Content-Type: application/json-roa+json; charset=UTF8 < Access-Control-Allow-Origin: http://127.0.0.1:8885 < Access-Control-Allow-Credentials: true < Access-Control-Allow-Headers: Content-Type, Accept, * < Access-Control-Allow-Methods?: CONNECT, DELETE, GET, HEAD, OPTIONS, POST, PUT, TRACE, * < Content-Length: 3713 …
Offending line is this header:
< Access-Control-Allow-Methods**?**: CONNECT, …
Fun fact: All the browsers and curl seemingly ignore it, but http from nodejs returns Error: Parse Error.
curl
http
Error: Parse Error
The text was updated successfully, but these errors were encountered:
I guess the superfluous colon is causing this: https://github.com/cider-ci/cider-ci_open-session_clj/blob/master/src/cider_ci/open_session/cors.clj#L30
There should be the same problem in the Madek API. I will fix it.
Sorry, something went wrong.
No branches or pull requests
o_O
Offending line is this header:
Fun fact:
All the browsers and
curl
seemingly ignore it, buthttp
from nodejs returnsError: Parse Error
.The text was updated successfully, but these errors were encountered: