Aller au contenu principal

Commentaires

4 commentaires

  • Commentaire officiel
    Ryan Cooney

    This particular service rejects requests that don't contain a User-Agent header. You can add one to your data source with the + button and it will work.

  • Ryan Kelley

    Thanks Ryan - that worked! I have similar issues with Workflow not returning results to drop down lists in forms with the same url. If I use the underlying server name and not the web adaptor for the url, the dropdown lists populate. How do I get around issue in workflow? Do I need to do a web request and add a user agent as a parameter? I am unsure.

    0
  • Ryan Cooney

    Hi Ryan,

    That is most likely a different issue. In a workflow running in a web browser there is no way to set your own user agent header. The browser will always assign this for you. 

    My first guess is that it would be a CORS related problem given that the request works for one host name and not another. The console errors and network traffic reported by your browser's developer tools should provide an indication.

    0
  • Ryan Kelley

    Thanks Ryan. I don't see any CORS blocks in the web traffic. This is also in the SaaS env, using https://apps.vertigisstudio.com/web.

     

     

    0

Vous devez vous connecter pour laisser un commentaire.