In an Explicit Proxy deployment, has anyone experienced and identified the reason of getting intermittent 401-Auth Required messages in the policy trace, with HEAD as the HTTP method and the URL being the actual explicit Proxy IP and port?
I have no idea at the moment what it could be. Would also be interesting to know what the client IP is (real client or MWG itself!?). In past, we had some cases where customer had proxy HA mode configured and a proxy loop was occurring based on mis-configuration, but as you mentioned, you are using explicit proxy mode, so this example should not matter. At the end, some more logs and the configuration itself should be checked via feedback file and this should not be uploaded here because of sensitive information. Please open a support case and attach the data there.
If you get a root cause and solution, please share it here for documentation purpose 🙂
Regards, Marcel Kutrieba Technical Support Engineer
If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.