Home/ Questions/Q 505171
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T06:34:16+00:00

I have a unit test for an Http handler. In it I create a

  • 0

I have a unit test for an Http handler. In it I create a HttpResponse object and pass it to one of my Http handler’s methods.

One of my tests attempts to verify that the response headers have been set correctly:

Assert.AreEqual( "gzip", response.Headers["Content-Encoding"]);

However, the Headers property throws a PlatformNotSupportedException with the message “This operation requires IIS integrated pipeline mode”.

The strange thing is that as I understand it, that exception is related to setting reponse headers – not reading them. I’m using TDD, so I don’t set the headers anywhere (yet), but still I’m getting the exception.

Why am I getting this exception and is there a good or better way to unit test response headers?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    From the Response.Headers documentation:

    Remarks

    The Headers property is only supported
    with the IIS 7.0 integrated pipeline
    mode and at least the .NET Framework
    3.0. When you try to access the Headers property and either of these
    two conditions is not met, a
    PlatformNotSupportedException is
    thrown.

    Basically you can’t even attempt to access it unless you’re running with those conditions.

    If I were you, I would create a constructor for your Handler that accepts an HttpContextBase object and use a mock in order to test your headers properly.

    • 0