Work-around data virtualization API with IIS

Hi ​@koenterralytics, thanks for your post. I’ll look into this and get back to you.

Hi again ​@koenterralytics, I unfortunately wasn’t able to reproduce this in b25835. I tried all four permutations of the IIS machine and Flow host machine using HTTP/HTTPS to be sure. 

Could you please send the following:

• A screenshot of the Swagger page when you try and open the docs.
• A screenshot of what’s shown when you press the yellow “Invalid” button.
• Screenshots of the POST /export endpoint in DevTools. The endpoint is unauthenticated so nothing confidential should be here (and session tokens are short-lived), but I recommend hiding the request headers just in case:

  

  

Feel free to submit a support ticket instead of sending information here if you would prefer!

Hi,

I changed a few things to test this:

1. Changed the get-endpoint of the api-spec from get to get1 to see what happens. (I did not remove the whole API-spec DV to avoid having to go through the steps again and you cannot temporarily disable a DV I think). As soon as I do this, I get the message from the second screenshot. So not the original Invalid button, but at least it shows that it is not working properly.

2. 

   

   Disable the rewrite rule in IIS. As soon as I do this, the servername in the swagger documentation changes to localhost:8080. So disabling the rule at least changes the swagger-api-documentation.