Hi,
When we make a request to get the GSTIN details using the paid GSTIN API, we get responses for 2 requests and then we get an error.... when we try after say 15 minutes we get responses for 2 requests and then start getting the error again.
The response we get from your server is:
CookieSpec selected: default Auth cache not set in the context Connection request: [route: {s}->https://www.knowyourgst.com:443][total kept alive: 0; route allocated: 0 of 2; total allocated: 0 of 20] Connection leased: [id: 34][route: {s}->https://www.knowyourgst.com:443][total kept alive: 0; route allocated: 1 of 2; total allocated: 1 of 20] Opening connection {s}->
Connecting to
Connecting socket to
with timeout 5000 Enabled protocols: [TLSv1, TLSv1.1, TLSv1.2] Enabled cipher suites:[TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS_RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256, TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_RSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA, TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA, TLS_EMPTY_RENEGOTIATION_INFO_SCSV] Starting handshake Secure session established negotiated protocol: TLSv1.2 negotiated cipher suite: TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 peer principal: CN=knowyourgst.com peer alternative names: [knowyourgst.com, www.knowyourgst.com] issuer principal: CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US Connection established 87.98.155.86:37090<->139.59.6.214:443 http-outgoing-34: set socket timeout to 5000 Executing request GET /developers/gstincall/?gstin=19AAACT3957G1Z4 HTTP/1.1 Target auth state: UNCHALLENGED Proxy auth state: UNCHALLENGED http-outgoing-34 >> GET /developers/gstincall/?gstin=19AAACT3957G1Z4 HTTP/1.1 http-outgoing-34 >> passthrough: Y3NyQGdsb2JhbDEwMTcxMjA0Njg http-outgoing-34 >> Host:
http-outgoing-34 >> Connection: Keep-Alive http-outgoing-34 >> User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121) http-outgoing-34 >> Accept-Encoding: gzip,deflate http-outgoing-34 >> "GET /developers/gstincall/?gstin=19AAACT3957G1Z4 HTTP/1.1[\r][\n]" http-outgoing-34 >> "passthrough: Y3NyQGdsb2JhbDEwMTcxMjA0Njg[\r][\n]" http-outgoing-34 >> "Host: www.knowyourgst.com[\r][\n]" http-outgoing-34 >> "Connection: Keep-Alive[\r][\n]" http-outgoing-34 >> "User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_121)[\r][\n]" http-outgoing-34 >> "Accept-Encoding: gzip,deflate[\r][\n]" http-outgoing-34 >> "[\r][\n]" http-outgoing-34 << "HTTP/1.1 400 Bad Request[\r][\n]" http-outgoing-34 << "Server: nginx[\r][\n]" http-outgoing-34 << "Date: Mon, 16 Jul 2018 08:33:34 GMT[\r][\n]" http-outgoing-34 << "Content-Type: application/json[\r][\n]" http-outgoing-34 << "Transfer-Encoding: chunked[\r][\n]" http-outgoing-34 << "Connection: keep-alive[\r][\n]" http-outgoing-34 << "X-Frame-Options: SAMEORIGIN[\r][\n]" http-outgoing-34 << "[\r][\n]" http-outgoing-34 << "d[\r][\n]" http-outgoing-34 << ""GSTIN error"[\r][\n]" http-outgoing-34 << "0[\r][\n]" http-outgoing-34 << "[\r][\n]" http-outgoing-34 << HTTP/1.1 400 Bad Request http-outgoing-34 << Server: nginx http-outgoing-34 << Date: Mon, 16 Jul 2018 08:33:34 GMT http-outgoing-34 << Content-Type: application/json http-outgoing-34 << Transfer-Encoding: chunked http-outgoing-34 << Connection: keep-alive http-outgoing-34 << X-Frame-Options: SAMEORIGIN Connection can be kept alive indefinitely Connection [id: 34][route: {s}->https://www.knowyourgst.com:443] can be kept alive indefinitely Connection released: [id: 34][route: {s}->https://www.knowyourgst.com:443][total kept alive: 1; route allocated: 1 of 2; total allocated: 1 of 20]
We are facing this only today.... earlier it was working just fine.
I'm not able to edit this Question.....in my response there is our API key... can you please mask it... I never extected this question to go public..... I thought this would be a support ticket.
I tried using Postman, but same 400 bad request error: "GSTIN error"
Now we are just getting an error.... we do not even get those 2 responses in 15 minutes.
this is my curl response:
curl -v -H "passthrough:APIKEY" https://www.knowyourgst.com/developers/gstincall/?gstin=19AAACT3957G1Z4
* Trying 139.59.6.214...
* TCP_NODELAY set
* Connected to www.knowyourgst.com (139.59.6.214) port 443 (#0)
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /opt/local/share/curl/curl-ca-bundle.crt
CApath: none
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* NPN, negotiated HTTP1.1
* 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, Unknown (67):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: CN=knowyourgst.com
* start date: May 26 03:27:20 2018 GMT
* expire date: Aug 24 03:27:20 2018 GMT
* subjectAltName: host "www.knowyourgst.com" matched cert's "www.knowyourgst.com"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
> GET /developers/gstincall/?gstin=19AAACT3957G1Z4 HTTP/1.1
> Host: www.knowyourgst.com
> User-Agent: curl/7.53.1
> Accept: */*
> passthrough:Y3NyQGdsb2JhbDEwMTcxMjA0Njg
>
< HTTP/1.1 400 Bad Request
< Server: nginx
< Date: Mon, 16 Jul 2018 10:53:05 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< X-Frame-Options: SAMEORIGIN
This is strange.
It is working fine at our end.
By any chance you have enabled cache at your end? Try to call API using POSTMAN. It is working perfectly.
I just tested 5 times in a second and returned data. You regularly face this issue or today only?
Sign up to discuss taxation, accounting and finance topics with experts from all over India.
Join Discussion