Skip to content
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

GET Request Responds with 400 Bad Request with Var in URL #2285

Closed
patrick-martin-shoutpoint opened this issue Aug 23, 2016 · 2 comments
Closed
Assignees

Comments

@patrick-martin-shoutpoint
Copy link

patrick-martin-shoutpoint commented Aug 23, 2016

  1. Postman Version: 4.6.2
  2. App (Chrome app or Mac app): Mac
  3. OS details: 10.11.5
  4. Is the Interceptor on and enabled in the app: No
  5. Did you encounter this recently, or has this bug always been there: Since last update
  6. Expected behaviour: 200 OK response
  7. Console logs (http://blog.getpostman.com/2014/01/27/enabling-chrome-developer-tools-inside-postman/ for the Chrome App, View->Toggle Dev Tools for the Mac app):
GET
https://api.shoutpoint.com/v1/LiveCalls/141793@4755
07:55:26.295
Error:
SSL Error: Hostname/IP doesn't match certificate's altnames: "Host: api.shoutpoint.com/v1. is not in the cert's altnames: DNS:api.shoutpoint.com, DNS:www.api.shoutpoint.com"

  1. Screenshots (if applicable)

400 Bad Request on GET requests, when I use a variable in the URL like this: https://{{BASE_URL}}/LiveCalls/:callId
BASE_URL = api.shoutpoint.com/v1

Error:
SSL Error: Hostname/IP doesn't match certificate's altnames: "Host: api.shoutpoint.com/v1. is not in the cert's altnames: DNS:api.shoutpoint.com, DNS:www.api.shoutpoint.com"

However, if I remove the variable and change the URL to https://api.shoutpoint.com/v1/LiveCalls/:callId, the request works.

@numaanashraf
Copy link
Member

@patrick-martin-shoutpoint Thanks for reporting this. We are looking into this and will keep you posted.

@PabloLedo97
Copy link

Buenas tardes, el problema que tengo, es que al hacer un GET al conjunto de recursos no me sale en ese conjunto un recurso que previamente habia creado correctamente mediante un POST. Cual podria ser el fallo gracias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants