Sign in Register
Go to solution
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • BenH 59 posts 199 karma points
    Feb 08, 2017 @ 17:04
    BenH
    0

    URL rewrite rules causing hang in front end

    I've added a single rewrite rule in my local copy (7.5.9) and upon pushing to the development environment, it causes the front end to produce a 502 bad gateway error. The redirect works on local perfectly.

    After some troubleshooting, we found that deleting the TEMP folder in App_Data gets the front end working again.

    Does anyone have any idea what could be happening??

    Below is the rewrite rule that I am placing just before the /system.webServer tag. 

    <rewrite>
  <rules>
    <rule name="allresources">
      <match url="^en-us/resources-insights/" />
      <action type="Redirect" url="en-us/resources/" appendQueryString="true" />
    </rule>
  </rules>
</rewrite>
    Copy Link
  • BenH 59 posts 199 karma points
    Feb 08, 2017 @ 21:59
    BenH
    100

    Solution was to add a stopProcessing="true" to each entry and order them by url length from longest to shortest. This ensures a link like /page/stuff/etc is processed before /page/stuff.

    This is an informative post about it: http://stackoverflow.com/questions/18927737/iis-redirect-rule-priority

    Copy Link
Please Sign in or register to post replies

Write your reply to:

Draft