Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Bypass Proxy Settings on MID server for Custom Cloud Management REST API - e.g. for WAP (Windows Azure Pack) - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Bypass Proxy Settings on MID server for Custom Cloud Management REST API - e.g. for WAP (Windows Azure Pack)
KB0713632

Bypass Proxy Settings on MID server for Custom Cloud Management REST API - e.g. for WAP (Windows Azure Pack)


1810 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Description


To build custom Cloud Management API, it's necessary extend MID Server Script Include CloudRESTAPIInvoker, as in its description:

Abstracted class for making REST API calls. Classes that implement this need to extend this object and provide overrides for getEndpointUrl to return the targeted endpoint, and for getHeaders and/or getParameters if there are headers and/or parameters to send with a request.


CloudRESTAPIInvoker uses another MID Server Script Include CloudAPIBase to check if MID server is configured with proxy. 
If MID server is using proxy, then the Custom API is forced to use proxy as well, by default.
This may break custom implementation like WAP (Windows Azure Pack), where the API is pointing to local servers, and the connection should not be going through web proxy.

 

Workaround


Create a new MID Server Script Include based on CloudRESTAPIInvoker, but without the proxy section starting at line: 
if (cloudApiBase._useProxy()) {
 
Also make sure to update the first two lines and the second last line to reflect new script include name.
 
Then, build custom API to extend this new file.
 
 

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.