I
Ilyas
Hi all
I have a simple httphandler :
public class TextFileHandler : IHttpHandler
{
public void ProcessRequest(HttpContext context)
{
context.Response.ContentType = "text/plain";
context.Response.Write("Text file handler");
}
public bool IsReusable
{
get
{
return false;
}
}
}
}
and in my web,config I have registered this handler using the
following:
<add name="TextFileHandlerName" verb="*" path="*.txt"
type="TestHttpHandlers.Usage.TextFileHandler" />
Now when I browse to any text file, I am expecting my handler to kick
on and intercept the request.
It doesnt happen when I run it under the built in Visual studio
asp.net development server, but it works under IIS7 (the above code
gets executed)
Does anyone know ehy it doesnt work the built in the visual studio
built in web server?
I have a simple httphandler :
public class TextFileHandler : IHttpHandler
{
public void ProcessRequest(HttpContext context)
{
context.Response.ContentType = "text/plain";
context.Response.Write("Text file handler");
}
public bool IsReusable
{
get
{
return false;
}
}
}
}
and in my web,config I have registered this handler using the
following:
<add name="TextFileHandlerName" verb="*" path="*.txt"
type="TestHttpHandlers.Usage.TextFileHandler" />
Now when I browse to any text file, I am expecting my handler to kick
on and intercept the request.
It doesnt happen when I run it under the built in Visual studio
asp.net development server, but it works under IIS7 (the above code
gets executed)
Does anyone know ehy it doesnt work the built in the visual studio
built in web server?