Why is my workflow URL prefixed with "http://myServer.com/Html5Viewer/proxy.ashx?" and I get a 403 error?

Sean McClurkan

3. Juni 2019 15:01

0

• 

  Stefan Schweigert

  3. Juni 2019 15:35

  Hi Sean,

   

  If you having configured GVH to use the proxy rules defined in the proxy.config file and are using permissions on your site, then requests will be routed through the proxy. Check to see if the URL that is used to run the workflow from is contained in the list of service URLs to be allowed access.

   

  Thanks, Stefan

  0
• 

  Sean McClurkan

  3. Juni 2019 15:55

  You’re a hero, Stefan. Thanks!

  0
• 

  Sean McClurkan

  19. März 2020 18:23

  So what happens when you do have the the URL the workflow is called from in the proxy.config file, but it still does the prefixing thing?

  0
• 

  Stefan Schweigert

  19. März 2020 20:18

  The workflow should use the proxy when run. Are you still seeing a 403?

  0
• 

  Sean McClurkan

  19. März 2020 20:38

  I caught an HTTP reference in the Run External Command activity going to an HTTPS server, so it was triggering the proxy.ashx? I think.

  0
• 

  Permanently deleted user

  25. März 2020 08:35

  Hi,

   

  Kindly please help me. I am having the same issue..I upgraded the html5 viewer to the latest 4.12.2 and the workflow 5 urls stopped working in the html5 viewer. Since all my servers are internal servers only I changed the setting in the proxy config to allow all that made the workflow 5 url to work without throwing the 403 error. But I think I need to do something else.

   

  Please help me.

   

  Thanks in adavance.

  0
• 

  Permanently deleted user

  25. März 2020 16:01

  Hi,

   

  Sorry my bad, simply I had to include the url of workflow 5 in the proxy config file and thats it.

   

  Thanks,

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.