Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Rohkem teavet

Teema arhiveeriti. Please ask a new question if you need help.

reverse proxy/URL Rewrite in IIS not supported by firefox?

  • 1 vastus
  • 1 on selline probleem
  • 3 views
  • Viimati vastas SHAIN

prasanna.ferrari
prasanna.ferrari
more options

I have a Angular 6 app hosted behind a reverse proxy in IIS. 

I'm unable to launch the app in iframe using firefox but can do so using chrome.

I've been using the URL Rewrite Module.

I have a Angular 6 app hosted behind a reverse proxy in IIS. I'm unable to launch the app in iframe using firefox but can do so using chrome. I've been using the URL Rewrite Module.

All Replies (1)

SHAIN
SHAIN
more options

I can't talk about Chrome but Firefox has, and has had for quite some time, a bug where it fails to recognise new content on some pages and uses it's cache instead. Just restarting the browser achieves nothing. You have to clear the browser cache completely. In some web apps I have to append a random or timestamped string to the URL in order to get FF to always reload some pages. The relevant meta tags in the header are very often also ignored by FF.

<rewrite> 

 <rules>
   <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>
 </rules>

</rewrite>