Curl "No status code specified in the response"

-
Sarps-Mac $ curl -vvv -X GET "https://jmd88pxp.execute-api.us-west-2.amazonaws.com/dev/user?limit=10"
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying 54.192.119.190...
* Connected to jmd88pxp.execute-api.us-west-2.amazonaws.com (54.192.119.180) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.execute-api.us-west-2.amazonaws.com
* Server certificate: Symantec Class 3 Secure Server CA - G4
* Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5
> GET /dev/user?limit=10 HTTP/1.1
> Host: jmd88pxp.execute-api.us-west-2.amazonaws.com
> User-Agent: curl/7.49.1
> Accept: */*
> 
< HTTP/1.1 502 Bad Gateway
< Content-Type: application/json
< Content-Length: 36
< Connection: keep-alive
< Date: Sun, 18 Dec 2016 00:54:14 GMT
< X-Cache: Error from cloudfront
< Via: 1.1 66ed69e8b47ad05050331602c798133a.cloudfront.net (CloudFront)

You need to provide a status code

const RESPONSE = {
  OK: {
    statusCode: 200,
    message: [],
  },
  ERROR: {
    status: 400,
    message: "Something went wrong. Please try again."
  }
};

Then your call will return successfully


Sarps-MacBook-Pro:serverless-framework sarp$ curl -vvv -X GET "https://jmd88pxp.execute-api.us-west-2.amazonaws.com/dev/user?limit=10"
Note: Unnecessary use of -X or --request, GET is already inferred.
*   Trying 54.192.119.31...
* Connected to jmd88pxp.execute-api.us-west-2.amazonaws.com (54.192.119.31) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.execute-api.us-west-2.amazonaws.com
* Server certificate: Symantec Class 3 Secure Server CA - G4
* Server certificate: VeriSign Class 3 Public Primary Certification Authority - G5
> GET /dev/user?limit=10 HTTP/1.1
> Host: jmd88pxp.execute-api.us-west-2.amazonaws.com
> User-Agent: curl/7.49.1
> Accept: */*
> 
< HTTP/1.1 200 OK
< Content-Type: application/json
< Content-Length: 0
< Connection: keep-alive
< Date: Sun, 18 Dec 2016 01:43:52 GMT
< X-Cache: Miss from cloudfront
< 
* Connection #0 to host jmd88pxp.execute-api.us-west-2.amazonaws.com left intact

Comments

Unknown said…
Wow, absolutely fantastic blog. I am very glad to have such useful information. Thanks. For more information visit legal herbal empire for sale
April 19, 2017 at 11:53 PM
rmouniak said…
This comment has been removed by the author.
December 3, 2018 at 2:22 AM
Post a Comment

Popular posts from this blog

AWS encryption chart (SSE-S3 vs SSE-KMS vs SSE-C)

-
IN TRANSIT AT REST SSL/TLS Server Side Managed Keys Client Side Managed Keys S3 (SSE-S3) Each object is encrypted with a key. Amazon encrypts the key with a master key, which rotates regularly. AWS Key Management Service (SSE-KMS) Allows you to audit trail (who and when used the key), extra cost and you manage the master key. Customer provided (SSE-C) User manages the keys but encryption done by Amazon User encrypts the data on client-side and uploads to S3
Read more

Space Character Problem on IE 6, 7, and 8

-
Most of the time, we need to put space in between two HTML elements to separate them. There are bunch of ways to achieve this but the following are the most common ones that I use: Space character ( ) CSS Margin (margin-right/margin-left) Space character is so natural separate them but CSS margin gives more flexibility. Also recently, I found out that in IE 6, 7, 8, extra space characters between HTML elements are not rendered as intended. For instance regular space character ( ) is rendered without the space on older version of IE (older than 9) a   b Result in IE 6, 7, 8: ab Whereas, if you use CSS (e.g. margin-right: 4px), all versions of IE renders it correctly a b Result in all IEs: a b
Read more

Sending Large Data with JSON

-
Image
On ASP.NET(v 4.0), there is default limit for JSON serialization and if you are exchanging large amount of data over JSON then you need to set the maximum length of JSON which can be sent/received before/after serialization. Here is the easiest way to set JSON length for serialization code which you can use in web.config file. This example sets the max length to ~2MB. <system.web.extensions> <scripting> <webServices> <jsonSerialization maxJsonLength="2000000"> </jsonSerialization> </webServices> </scripting> </system.web.extensions>
Read more