How to avoid 'HTTP 303 See Other' response from Apigee Edge UI

Not applicable

Hello,

Could anyone please advise me on how to resolve the issue of the customer who see the following response from Apigee Edge Management Server on Private Cloud.

HTTP/1.0 303 See Other Cache-Control: no-cache Location: https:///login Set-Cookie: PLAY_SESSION="b6ec29a...\;Expires=Tue,05.Apr.2016.01:50:59.GMT;Path=/ X-Frame-Options: DENY Content-Length:0

This response is given against the health check packet sent from load balancer to Management Server by;

http://<ms-ip>:9000/login

Normal login to MS UI is ok and they want to get the same response of '200 OK' for the above health check. Is there any way to configure MS UI or whatever to enable it?

0 4 865
4 REPLIES 4

Not applicable

Hi Toshi,

What is the LB hitting?, which URL?

Hi Maudrit,

Thank you for picking up this question. There was some confusion I made on what the customer wants to do.

Let me please rewrite this question as follows.

The load balancer connected to each host sends HTTP request for the health check without 'Host:' header. In the case of Management Server with a call like http://<ms-ip>:9000/login will respond with '303 See Other'. It is regarded as ok, but in the case of router against the request http://<router-ip>:9001/<apiproxy-path>;,

the response will be '400 Bad Request' with the body;

{"fault":{"faultstring":"Missing Host header","detail":{"code":"MISSING_HOST"}}}

They want to avoid '4xx' reponse, since the load balancer see the status is NG, but both 2xx and 3xx are ok.

So, could you advise us on what request path and/or configurations on router we can get the response of '2xx' or '3xx' against the health check call to routers?

They need to check against the same port like 9001 used for the virtual host of the apiproxy calls.

Not applicable

Toshi , you can try setting the "TCP" health checks on the load balancers in stead of "http".

Thanks a lot Naveen.

I'll double check with them, but as I explained they want to check by HTTP with a path specified and the same virtual host port used by apiproxy calls.

So, TCP health check can not be an option. So, again is there any way to configure requests without "Host:" header with a specific path or config which we can get 2xx/3xx back from router against http://<router-ip>:<port>/<path>; sent by the load balancer?