Forum Discussion
NimbostratusAPM my.policy comes up in 400 error (solved)
Having an issue with APM logon page on v10.2. I created a policy that consists of the standard logon page, connected to an AD auth. When I hit the VS, the my.policy page loads up with the following message:
Bad request!
Your browser (or proxy) sent a request that
this server could not understand.
Error 400
I have looked around on devcentral, but have not found anything that quite matches what I'm seeing. I've also had no luck in the logs.
Can anyone shed some light on what's going on with the logon page?
Thanks
--UPDATE--
Found I was missed a setting on the VS. See last post.3 Replies
- Kevin_Stewart
Employee
Do you have any special settings in your logon page? Do you go through a forward proxy to get to the APM VIP? The next thing I'd suggest is running a local HTTP inspection engine like Fiddler or HTTPWatch in the browser to see what that conversation looks like. In other words, what is the request that immediately precedes the 400 error?
- Kevin_Stewart
Very interesting. I suppose technically per RFC a Location header should be a complete URL but a URI value doesn't break most browsers. Is this a browser client? And does Fiddler show the 400 message coming from APM?
Rik_Koenig_7777Saw that Port Translation was unchecked on the VS. After enabling it, the logon page has come up correctly. If new info comes up, I will update.
Thank you for your help!
