To do this, click on the \’ where you will need to replace with the IIS server URL accessible to your users. Since JavaScript encoded content is text/application-javascript, the easiest way to work around this limitation is to change the precondition to match responses with the content type of type text/* - text followed by slash anything. This precondition matches any responses coming from the back-end server that have the response content type set to text/html. If you click on the ‘Edit’ button next to the ResoponseIsHtml1 precondition, we can see the configuration of the precondition.
#Sonarr setup wizard series#
If we look at the ‘ReverseProxyOutboundRule1’ in the rules section of URL Rewrite, rule which was created in the Reverse Proxy wizard we ran in part 1 of this blog series and we check the Preconditions associated with this rule, we will see that a precondition was created during the Reverse Proxy setup wizard, the precondition is called ResponseIsHtml1. Note the \ (inverted slash) before each of the values of the href and action attributes. Below are examples of such snippets of code: This content might include such things as Anchor tags, or form tags which have action attributes. More and more applications send content to the browser in the form of JavaScript encoded content, which the JavaScript running in the page that has requested the content then integrates into the DOM (Document Object Model) of the page.
![sonarr setup wizard sonarr setup wizard](https://smarthomepursuits.com/wp-content/uploads/2020/01/image-7.png)
Check out part 1 and part 2 before reading on.Ĭonfiguring outbound rules for Javascript encoded content. This is the third part of the article series dealing with IIS using URL rewrite as a reverse proxy for real world apps.