oData feed with paging and a reverse proxy

We have an on-premise app with IIS setup along with the URL rewrite module which servers as our reverse proxy. This effectively rewrites the requests made to the IIS website to our mendix app. My issue is when an oData feed has paging enabled, the URI link to the next set of data is also rewritten, and our BI app can't continue to retrieve the data and follow the links. I know we need some kind of outbound rule to change the URIs back, but can't seem to figure it out :-( would appreciate a nudge in the right direction from someone with the relevant experience Here's what I've got so far: <outboundRules> <rule name="FixODataURIs" preCondition="ContentTypeMatch" patternSyntax="ExactMatch" stopProcessing="true"> <match filterByTags="None" pattern="localhost:8080/" /> <action type="Rewrite" value="our.app.url/" /> <conditions> <add input="{URL}" pattern="^/odata/.*" /> </conditions> </rule> </outboundRules> Edit - Found the solution: <outboundRules> <rule name="FixODataURIs" preCondition="ContentMatching" enabled="true" patternSyntax="ExactMatch"> <match filterByTags="None" pattern="http://localhost:8080/" /> <conditions> </conditions> <action type="Rewrite" value="https://our.app.url/" /> </rule> <preConditions> <preCondition name="ContentMatching"> <add input="{RESPONSE_CONTENT_TYPE}" pattern="^application\/atom\+xml" /> <add input="{REQUEST_URI}" pattern="^(.*)odata/(.*)" /> </preCondition> </preConditions> </outboundRules>
1 answers

There is a setting in IIS in the application request routing settings called something like inspect requests and rewrite urls.

I am not sure if this would fix your isue but it's worth checking,