Hello @Wagner1991 ,
have you ensured that for these specific URL hosts HTTPS scanning is bypassed so that header can be seen and rewritten for that?
Further details can be taken from this post as well:
https://community.mcafee.com/t5/Web-Gateway/Implementing-Tenant-Restrictions-for-Microsoft-Office-36...
In case you need further assistance, debug data is definitively needed but not here in community.
I would suggest to reproduce issue and generate a rule trace and open a SR along with feedback file so that we in support can check this.
FEEDBACK FILE
1) Navigate to "Troubleshooting" > select the MWG you are testing on > "Feedback"
2) Keep the option "Pause running McAfee Web Gateway to create a backtrace (recommended)" enabled (this will NOT stop any service!)
3) Click the "Create Feedback File" button. This way we get your policy, configuration and debug information.
Via CLI:
# /opt/mwg/bin/feedback.sh -l 2
RULE TRACE
1) Navigate to "Troubleshooting" > "Rule tracing central"
2) Select the MWG which currently processes your traffic and enter the client IP you are testing with
3) Press the "Go" button, reproduce the issue and stop the rule trace afterwards
4) Click on "Export" > "Export visible traces..."
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!