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

perfops curl does not support Content-Type: text/plain;charset=UTF-8 #38

Open
julienlau opened this issue Nov 28, 2018 · 5 comments
Open
Labels

Comments

@julienlau
Copy link

julienlau commented Nov 28, 2018

Hi,
I really appreciate the tool, but I think the content-type is hard coded as :
Content-Type: application/json
Which makes my api return 404 instead of 200 if for example I serve only plain text.
Thanks and regards

@julienlau julienlau changed the title Example of perfops curl command needed perfops curl does not support Content-Type: text/plain;charset=UTF-8 Nov 28, 2018
@jimaek
Copy link
Contributor

jimaek commented Nov 28, 2018

Hey, are you sure about this? We use regular curl in the backend with default settings

@julienlau
Copy link
Author

julienlau commented Nov 28, 2018

Hi,

Thanks for quick answer. No I am not sure, but I cannot understand why I get this behaviour:


curl -v https://prd-gra-ladon.x.com/foo/bar

  • Trying 51.75.14.41...
  • TCP_NODELAY set
  • Connected to prd-gra-ladon.x (51.75.14.41) port 443 (#0)
  • ALPN, offering h2
  • ALPN, offering http/1.1
  • TLSv1.2 (OUT), TLS handshake, Client hello (1):
  • TLSv1.2 (IN), TLS handshake, Server hello (2):
  • TLSv1.2 (IN), TLS handshake, Certificate (11):
  • TLSv1.2 (IN), TLS handshake, Server key exchange (12):
  • TLSv1.2 (IN), TLS handshake, Server finished (14):
  • TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
  • TLSv1.2 (OUT), TLS change cipher, Client hello (1):
  • TLSv1.2 (OUT), TLS handshake, Finished (20):
  • TLSv1.2 (IN), TLS handshake, Finished (20):
  • SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
  • ALPN, server accepted to use http/1.1
  • Server certificate:
  • subject: CN=prd-gra-ladon.x
  • start date: Nov 12 11:52:02 2018 GMT
  • expire date: Feb 10 11:52:02 2019 GMT
  • subjectAltName: host "prd-gra-ladon.x.com" matched cert's "prd-gra-ladon.xcom"
  • issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
  • SSL certificate verify ok.

GET /foo/bar HTTP/1.1
Host: prd-gra-ladon.com
User-Agent: curl/7.60.0
Accept: /

< HTTP/1.1 200 OK
< Content-Type: text/plain;charset=UTF-8
< Content-Length: 64
< Connection: keep-alive
< X-RateLimit-Remaining-second: 9
< X-RateLimit-Limit-second: 10
< X-Kong-Upstream-Latency: 1
< X-Kong-Proxy-Latency: 1
< Via: kong/1.0.0rc3


perfops curl -v https://prd-gra-ladon.x.com/foo/bar
Node281, AS46562, Phoenix, United States
perfops: No output from the server. Try the -I parameter.\n


perfops curl -I -v https://prd-gra-ladon.x.com/foo/bar
Node241, AS40676, Ashburn, United States
HTTP/1.1 404 Not Found
Date: Wed, 28 Nov 2018 12:53:43 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Server: kong/1.0.0rc3
Content-Length: 58

@jimaek
Copy link
Contributor

jimaek commented Nov 28, 2018

Is that domain supposed to be working? I am getting a DNS error when trying to open it. It cant resolve the domain

@julienlau
Copy link
Author

Sorry no, it is not a public domain. I can PM it to you, but I won't keep it running for very long.
It is a server running: docker run -ti --rm -p 5050:5050 vad1mo/hello-world-rest

@jimaek
Copy link
Contributor

jimaek commented Nov 29, 2018

Ok, we will run our tests to debug this. Currently I can't see the problem but I will have my team to check as well.

@astrolox astrolox added the bug label Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

3 participants