By using AWS re:Post, you agree to the Terms of Use
/API Gateway Content Type issue/

API Gateway Content Type issue


Hi Team , We wanted to expose PingAccess Console via APIGateway.

We have below flow : Internet --> AWS API Gateway --> Private NLB --> EC2(Hosted PingAccess Admin Console)

We have deployed AWS API Gateway REST API with proxy integration and VPC link configuration but we are no able to open the same using API Gateway Endpoint.

We are getting below error in Browser.

Refused to apply style from '' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

We have added Content-Type in Response Headers and remove application/json from Content-Type option in Method Response tag.

Note: We are able to open PingAccess Console from NLB , with creating Public NLB.

1 Answers

Are you using Proxy Resource?

Seems like your issue is that API gateway is not forwarding the URL path to NLB, so your backend is always returning the content of (which most likely is an HTML page)

If you don't want to specify all possible URL path in the API gateway, using proxy resource is the way to capture all URL suffix and forward to the backend.

answered 23 days ago
  • Hi RichardFan , Thanks for responding. YES, we are using Proxy resource and we have mention greedy Proxy path {proxy+} to handle all context paths.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions