ng-http | Helper methods for Angular2 HTTP | HTTP library

The timeout was due to a misnamed ECR which the bookService was attempting to access. To generalize this answer a bit, if there's a timeout it may be good to record which resources timed out and sanity check all the constituent elements.

I think you need to pass $curl to the curl_getinfo method, not the $response

Chris,

I haven't used linode or kong and don't know what your frontend actually does, so I'll just point out what I can see:

• The simplest dns check is to curl (or ping, dig, etc.):

  • http://[dataapi's pod ip]:80 from a host node
  • http://[kong-proxy svc's internal ip]/dataapi/api/values from a host node (or another pod - see below)

• default path matching on nginx ingress controller is pathPrefix, so your nginx ingress with path: / and nginx.ingress.kubernetes.io/rewrite-target: / actually matches everything and rewrites to /. This may not be an issue if you properly specify all your ingresses so they take priority over "/".

• you said 'using a kong ingress as a proxy to redirect incoming', just want to make sure you're proxying (not redirecting the client).

• Is chrome just relaying its upstream error from frontend-service? An external client shouldn't be able to resolve the cluster's urls (unless you've joined your local machine to the cluster's network or done some other fancy trick). By default, dns only works within the cluster.

• cluster dns generally follows [service name].[namespace name].svc.cluster.local. If dns cluster dns is working, then using curl, ping, wget, etc. from a pod in the cluster and pointing it to that svc will send it to the cluster svc ip, not an external ip.

• is your dataapi service configured to respond to /dataapi/api/values or does it not care what the uri is?

If you don't have any network policies restricting traffic within a namespace, you should be able to create a test pod in the same namespace, and curl the service dns and the pod ip's directly:

After enabled HTTP 2.0 in your webapp, you need clear cookies and sessions, then you will find your webapp is works fine with HTTP/2 . Or wait a little longer.

1. You can open a new inprivate window, it works for me.

2. The second question is that enabling HTTP 2.0 will not have a negative impact on your application.

Related Posts：

① Will HTTP/2 in Azure App Service auto fallback to HTTP/1.1 for legacy browsers

3. The third point, there are also considerations about the correct version of .Net Framework, 4.6.2 and above all support HTTP 2.0.

I have tested that HTTP Version is supported in .NET Framework 4.6.2 and above. So your first question, you can open the privacy window and try again.

The article you reference assumes the backend is static (e.g. S3) and cannot set headers. That's why Lambda@Edge is used.

It sounds like your current setup should work without any changes... Did you try adding headers in the code?

I have this code working perfectly for the APIGW + Lambda (proxy integration) combo.

You should reference the model name and not the collection name:

I've done some test and hope it could help, if I misunderstood in some place, pls point it out.

First I created a http trigger function, when I called GET https://xxx.azurewebsites.net/api/HttpTrigger1?name=asdfg, I would get the response like hello asdfg.

Then I followed this doc to enable authentication via azure ad. That means I create a new azure ad app, expose an api like this.

After this step, when I call the GET request, it asks me to sign in then I can get the same response. Next I created another azure ad app and add api permission of the api I exposed just now, and via this application, I can generate access token with the scope of that api, and with this access token in the Authorization request header, I can access the GET request directly.

I finally was able to find complete documentation. I eventually stumble upon:

• API Gateway - PORT multipart/form-data

which refers to:

• Enabling binary support using the API Gateway console

The above documentation specify the steps to handle binary data. Pay attention that you need to base64 encode the response from lambda to pass it to API Gateway.

Well, a few key lessons I learned here:

1. Best way to debug (non-responsive) JavaScript is browser's More tools > Developer Tools > Console tab. Without this, I was flying blind.
2. The problem was not with the JavaScript, but rather with the security headers I was adding. I had followed this AWS article without a deep understanding of the directives, and they blocked my JavaScript.
3. Inline JavaScript is bad! Make sure you put all your scripts into a separate file. Maybe this is obvious to you, but I had to read this article to understand why. Plus I have seen many Stack Overflow questions with inline JavaScript, so I question if this is really well known...
4. Use the Mozilla Observatory and Google's CSP Evaluator to check and improve your website's security.

In the end, I used the following Content-Security-Policy headers: