Aws api gateway answers status 206 when I call service from my application and it answers 200 status when I call service from postman

0

I am using the api gateway of amazon, as a proxy for a URL on another server, everything has gone perfect,

  • the configuration of the resource in api gateway request_warranty
  • then the method associated with that GET resource
  • then indicate that it is an http proxy
  • then probe with the client for tests that provide amazon and work perfect
  • then I went to postman and provided the staging url that associates the api gateway

All good until then, then when I try to consume the service from my app created in swift , what I get is the following

{ URL: https://gk37imtq1g.execute-api.us-west-2.amazonaws.com/dev/request_warranties } { Status Code: 206, Headers { "Cache-Control" = ( "No-Cache" ); "Content-Encoding" = ( gzip ); "Content-Length" = ( 1521 ); "Content-Type" = ( "text/html; charset=utf-8" ); Date = ( "Fri, 17 Aug 2018 18:14:14 GMT" ); Expires = ( 0 ); Pragma = ( "No-Cache" ); "Set-Cookie" = ( "NS_ROUTING_VERSION=LEADING; path=/" ); "Strict-Transport-Security" = ( "max-age=31536000" ); Vary = ( "User-Agent" ); "edge-control" = ( "no-store" ); "ns_rtimer_com2018-08-17 13:14:14.987381-0500 WorkshopKavak[2134:12107642] TIC Read Status [5:0x0]: 1:57 posite" = ( "817249560:706172746E6572733031362E2018-08-17 13:14:14.987557-0500 WorkshopKavak[2134:12107642] TIC Read Status [5:0x0]: 1:57 70726F642E7365612E6E65746C65646765722E636F6D:80" ); p3p = ( "CP=\"CAO PSAa OUR BUS PUR\"" ); "x-amz-apigw-id" = ( "Lx-CTErEvHcFUKg=" ); "x-amzn-remapped-connection" = ( "Keep-Alive" ); "x-amzn-remapped-content-length" = ( 1521 ); "x-amzn-remapped-date" = ( "Fri, 17 Aug 2018 18:14:13 GMT" ); "x-amzn-requestid" = ( "583cec7a-a249-11e8-95ec-79d678f3aa07" ); "x-n-operationid" = ( "5bed340d-32de-4316-8e94-f2b1295b9bb8" ); } }

The funny thing about this is that if I consume a service that has a lambda associated with it, it does not give the answer 206, but 200

I want to know how I do so that this route answers 200, instead of 206 when I call it from my app

    
asked by German 17.08.2018 в 20:22
source

0 answers