Solved: "301 Moved Permanently" error from target server w...

Report Inappropriate Content · 07-18-2017 04:12 PM

Hello All, I'm a newbie to APIgee. I'm encountering "301 Moved Permanently" error (see below the complete HTML) in the APIgee Trace when API proxy (with auth token / basic authentication) hits the target server/service. When I hit the same target service from a REST client with the same authentication token I do get a valid response (200 status code). Can any one point me where I'm missing?

I'm using the trial APIgee cloud version.

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

Report Inappropriate Content

My bad - Targetserver was configured to http port(80) instead of https port(443) in the test env.

View solution in original post

snehal_chakrabo

Hi @Ramchander Chopperla

Ideally you should not get 2 separate responses. 301 means the url has changed. Switch on trace in your proxy and check the url being invoked from the target request flow

Report Inappropriate Content

My bad - Targetserver was configured to http port(80) instead of https port(443) in the test env.

"301 Moved Permanently" error from target server with a basic auth/auth token