Using API v2 /repositories file doesn't seem to work right now

Issue #19102 closed
Justin Dawson created an issue

I am using the following:<org_name>/<repo_name>/src/master/<path-to-file>/<filename>.yaml

this worked at least 8 hours ago, but no longer works.
doing a curl -u <username>:<password> with the above url, returns with no errors, and no data (instead of giving the contents of the expected file)

adding the verbose flag to the curl shows this

User-Agent: curl/7.58.0Accept: /

(304) (IN), TLS Unknown, Certificate Status (22):

(304) (IN), TLS handshake, Newsession Ticket (4):

(304) (IN), TLS Unknown, Unknown (23):

Connection state changed (MAX_CONCURRENT_STREAMS updated)!

(304) (OUT), TLS Unknown, Unknown (23):

(304) (IN), TLS Unknown, Unknown (23):

(304) (IN), TLS Unknown, Unknown (23):< HTTP/2 401< server: nginx

Authentication problem. Ignoring this.< www-authenticate: Basic realm=" HTTP"< content-type: text/html; charset=utf-8< strict-transport-security: max-age=31536000; includeSubDomains; preload< date: Thu, 11 Jul 2019 20:49:58 GMT< x-served-by: app-142< x-static-version: 8b902c173ec1< etag: "d41d8cd98f00b204e9800998ecf8427e"< x-render-time: 0.198377847672< x-version: 8b902c173ec1< x-request-count: 132< x-frame-options: SAMEORIGIN< content-length: 0

Comments (1)

  1. Justin Dawson reporter

    turns out the credentials that we were using were removed from our project.

    It would be nice to see a more explicit error when authentication fails on the api calls

  2. Log in to comment