When we attempt to perform a test connection with a base URL we get a HTTP Error Code 302 redirect error. When we place the URL directly in the browser it returns a 404 Error. When we check the port the server is on it shows it is listening as well. How do we get around the redirect in the Webservice Source?
Have you tried testing this endpoint in a tool such as Postman?
Hi Adam,
Yes sir - the endpoint works fine in Postman when using the desktop agent but if I use the cloud agent or the browser agent it gives me the message "Mixed Content Error: The request has been blocked because it requested an insecure HTTP resource" ! or CORS Error: The request has been blocked because of the CORS policy when using HTTPS
Have you seen these errors before? It keeps pointing to the server side but want to make sure
Hi @P96337,
From the screenshots and the information provided, it seems like you’re trying to reach a local resource.
For this, you would have to use the Webservices Connector (non-SaaS) and ensure the VA cluster is in the same network as the local resource.
To handle the 302 redirect, I would recommend writing a Webservices After Operation Rule.
Hope this helps!
Thanks for chiming in Kartik - much appreciated. I will give this a go and keep you posted.
No problem @P96337 
Let us know how it goes!
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.