Symantec Access Management

 View Only
Expand all | Collapse all

Chrome not setting Proxy-Authorization header while testing from API Explorer

  • 1.  Chrome not setting Proxy-Authorization header while testing from API Explorer

    Posted Nov 25, 2019 08:11 AM
    Hi all,

    I'm doing testing from API Explorer in Portal. I have a swagger file which has apikey,apikeysecret and Proxy-Authorization passed as headers in the file. Even though i'm passing all the headers with values, I'm getting response "Missing Proxy-Header info". When i open chrome console, i see this error: Refused to set unsafe header "Proxy Authorization".
    Same file works fine and provides expected response from Postman.  

    What is the solution for this?

    Thanks,
    Akash


  • 2.  RE: Chrome not setting Proxy-Authorization header while testing from API Explorer
    Best Answer

    Broadcom Employee
    Posted Nov 25, 2019 03:55 PM
    Akash, Not sure what the exact solution is. As a workaround...Can you try this pass XMLHttpRequest: setRequestHeader() ->>for headers that are forbidden. 
    setRequestHeader() sets the value of an HTTP request header; when using setRequestHeader() , you must call it after calling open() , but before calling send().
    Take care.