HTTP to HTTPS Rewrite Issues with Exchange 2016 [Answered]RSS

4 replies

Last post Jan 29, 2020 05:29 AM by Jalpa Panchal

  • HTTP to HTTPS Rewrite Issues with Exchange 2016

    Jan 07, 2020 03:17 AM|Legacy777|LINK

    Hi Everyone,

    I've got an Exchange 2016 server that I'm using for webmail access as well as hosting our website.  I have a rewrite rule to redirect http traffic to https. 

    <rule name="Redirect to HTTPS" stopProcessing="true">
    	<match url="(.*)" />
    	<conditions>
    		<add input="{HTTPS}" pattern="^OFF$" />
    	</conditions>
    	<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
    </rule>

    The rule works fine, however I'm running into issues with some of the services that run related to Exchange.  Powershell scripts connecting to exchange don't work and some other items I noticed in the log files.  I've posted some snippets from the logs below.  I guess my question, is there any modifications or tweaks to the rewrite rule that can be done that won't affect Exchange?  The only option I can think of is to create a separate site in IIS to move the regular website to and leave the default website with Exchange. 

    2020-01-06 00:00:15 192.168.1.37 GET /powershell ping=probe&CorrelationID=<empty>; 443 - 192.168.1.37 - - 401 111 0 13
    
    2020-01-06 00:00:25 127.0.0.1 GET /PowerShell/ &CorrelationID=<empty>; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 401 111 0 15
    
    2020-01-06 23:59:58 fe80::5ddd:2033:9069:dd92%6 RPC_IN_DATA /rpc/rpcproxy.dll 45c1e908-7e0c-45fe-8022-8c37565c241d@domain.com:6001&CorrelationID=<empty>;&RequestId=ff81bd3b-231a-43da-90de-689d467a0755&cafeReqId=ff81bd3b-231a-43da-90de-689d467a0755; 443 - fe80::5ddd:2033:9069:dd92%6 MSRPC - 401 1 2148074254 1
    
    2020-01-06 23:59:58 fe80::5ddd:2033:9069:dd92%6 RPC_OUT_DATA /rpc/rpcproxy.dll 45c1e908-7e0c-45fe-8022-8c37565c241d@domain.com:6001&CorrelationID=<empty>;&RequestId=68615a29-35b5-464f-b7e0-aa2261c1f380&cafeReqId=68615a29-35b5-464f-b7e0-aa2261c1f380; 443 - fe80::5ddd:2033:9069:dd92%6 MSRPC - 401 1 2148074254 0

    Any suggestions or thoughts on other options?

    Thanks in advance!

    Josh

  • Re: HTTP to HTTPS Rewrite Issues with Exchange 2016

    Jan 08, 2020 02:18 AM|Jalpa Panchal|LINK

    Hi,

    First status codes indicate that they were not generated by IIS, but custom ISAPI/modules.

    and the second 401.1 means Login failed. 

    I think you should better post it to an exchange forum where you can get better answers.


    http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver%2Cexchange2010%2Cexchangeserverlegacy


    Hope it can help you.

    Regards,

    Jalpa

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
  • Re: HTTP to HTTPS Rewrite Issues with Exchange 2016

    Jan 09, 2020 01:53 AM|Legacy777|LINK

    Thank you for the feedback.  I will ask there.

  • Re: HTTP to HTTPS Rewrite Issues with Exchange 2016

    Jan 29, 2020 03:56 AM|Legacy777|LINK

    I wanted to follow up on this question; I asked over on the Exchange forums and really didn't get any additional feedback.

    What I ended up doing is setting up a separate IIS site with different host headers using a subdomain and moved the main website over to it.  I've left the default website with OWA alone and everything appears to be working correctly.


    Thanks
    Josh

  • Re: HTTP to HTTPS Rewrite Issues with Exchange 2016

    Jan 29, 2020 05:29 AM|Jalpa Panchal|LINK

    I am glad that your issue is resolved. 

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.