Re: ExecuteUrlHeaders don't seem to matter
- From: Dimitri Glazkov <DimitriGlazkov@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Jan 2007 05:00:01 -0800
Bruce,
Thanks for responding -- I appreciate your effort.
Unlucky for me, all of that other stuff already works. The mapping's in
place, the DefaultWebHandler is being called as it is supposed to, and some
additional Reflectoring shows that the ExecuteUrlHeaders are being sent for
processing to
ISAPIWorkerRequestInProcForIIS6.BeginExecuteUrl(..), which in turn sends
them to
UnsaveNativeMethods.EcbExecuteUrlUnicode(..), which is a rabbit hole, being
the native code and all.
See, this guy hands control of the request back to IIS6, and I am wondering
if the headers are even being passed to it, and what restrictions and proper
use guidelines are of this functionality.
So, my question really should be restated to: "Has anybody ever successfully
used ExecuteUrlHeaders collection to modify/add header information in
DefaultWebHandler?"
Does this make sense?
P.S. Speaking of the next version of IIS. IIS7 integrated pipeline doesn't
even use this capability (ExecuteUrlHeaders collection, that is).
:DG<
"bruce barker" wrote:
then you have to map the page to asp.net handling or your handler will.
not be called (see your iis settings). there is a performance cost to
having asp.net serve static html which is why its not done by default.
note: the next release of iis will allow iis handlers to be written in
..net, so you will not need to map the files to asp.net to get the feature.
-- bruce (sqlwork.com)
Dimitri Glazkov wrote:
The page that the DefaultHttpHandler handles is a static HTML page.
:DG<
"bruce barker" wrote:
be sure the page code does not clear the headers.
-- bruce (sqlwork.com)
Dimitri Glazkov wrote:
Ok, help me out here. Here I am, coding under innocent assumption that
DefaultHttpHandler.ExecuteUrlHeaders are passed to the IIS6, per
documentation. Bu the thing is, they don't seem to. No matter what I put in
that collection, nothing gets into the HTTP response:
public override string OverrideExecuteUrlPath()
{
ExecuteUrlHeaders.Add("X-Frustration", "work, dammit");
return Context.Request.ApplicationPath + _path;
}
What gives? Anybody has any pointers/helpers?
- References:
- Re: ExecuteUrlHeaders don't seem to matter
- From: bruce barker
- Re: ExecuteUrlHeaders don't seem to matter
- From: bruce barker
- Re: ExecuteUrlHeaders don't seem to matter
- Prev by Date: Asymmetric Encryption
- Next by Date: Adding custom application installable as the pre-requisite in VS2005 deployement project
- Previous by thread: Re: ExecuteUrlHeaders don't seem to matter
- Next by thread: edit and Inserted Item in DetailsView
- Index(es):
Relevant Pages
|
Loading
