Symantec Access Management

Expand all | Collapse all

Custom headers not passed - IIS 8 - 12.52 WA

Jump to Best Answer
  • 1.  Custom headers not passed - IIS 8 - 12.52 WA

    Posted 03-06-2017 10:31 AM

    A custom header has been set for an IIS 8 based site protected by a 12.52 Webagent (Build 142).

     

    Although the header is defined in the response it is not passed to IIS. Legacy headers are also not passed to IIS however they are enabled in the ACO.



  • 2.  Re: Custom headers not passed - IIS 8 - 12.52 WA

    Posted 03-06-2017 11:02 AM

    Hi Matthew

    There may actually be several reasons for this not working, like incorrect directory mappings or agent name resolution, etc. I believe we would need the policy server trace showing the transaction not passing the headers, the webagent trace as well as a fiddler trace for this. Likely you may want to open a support case to have a more thorough investigation



  • 3.  Re: Custom headers not passed - IIS 8 - 12.52 WA

    Posted 03-06-2017 11:15 AM

    1. Is the response getting triggered properly on PS side?

    2. Was the website configured with CA SSO webagent configuration wizard or manually? Can u share applicationHost.config & web.config?

    3. How are you reading headers? 

    4. Do you have any custom modules other than CA SSO configured in IIS?

    5. Does it work in classic pipeline mode?



  • 4.  Re: Custom headers not passed - IIS 8 - 12.52 WA
    Best Answer

    Posted 03-06-2017 03:25 PM

    Upgrading webagent to 12.52 SP1 CR6 resolved issue.



  • 5.  Re: Custom headers not passed - IIS 8 - 12.52 WA

    Posted 03-06-2017 03:58 PM

    Ah right, 12.52 base (build 142) does not support IIS 8.0.