Use HttpHandler or HttpModule?

养狗的上帝

Not very familiar with HttpHandler and HttpModule. Now I want to implement the following functions:

When a user requests something like: /Info/Detail/*/*/*/*.aspx, such as
/Info/Detail/2016/06/30/1584587.aspx, I first determine whether the file exists, if it does not exist, create it, otherwise visit the page directly. Functions similarly to file system caching.

I now use HttpHandler to handle it and find that the file has been created, but the content of the window to access the page is blank. If you move the created file to another directory, such as / Info /, you can access it. Later I added after the creation of MyHandler's ProcessRequest:
context.Response.Redirect (context.Request.Path);
It doesn't work, it will cause an endless load ~~

What should I do, or should I use HttpModule?

I kindly ask for your thoughts, thank you! !! !!

orclee

Use HttpHandler, or HttpHandlerFactory.

mgcfox

It is true to use HttpHandler to process certain types of files.
However, if the file /Info/Detail/2016/06/30/1584587.aspx does not exist, IIS directly returns a 404 error to the client, and will not pass the request to aspnet_isapi.dll for processing, nor will it be passed to you to write HttpHandler.
I think your description is a bit strange.

shenmue024

Agree withmgcfox

But * .aspx can still go to HttpHandler if it doesn't exist.
If it is something else, it won't work. Because * .aspx is still explained through asp.net.

Others will not work. Iis. Direct report does not exist.

hunqiu223

Use IO to judge. Then use server.transfer () to transfer.

养狗的上帝

Thank you for your reply upstairs, my code is as follows:
public void ProcessRequest (HttpContext context)
{
string strFilePath = context.Server.MapPath (context.Request.Path);

bool blnRebuild = false;
if (! File.Exists (strFilePath))
{
blnRebuild = true;
}

if (blnRebuild)
{
// Extract information ID
long lngInfoID = GetInfoIDByPath (context.Request.Path);
CreateInfoDetailPage (lngInfoID, strMainWebRootPath);
}

if (! File.Exists (strFilePath))
{
context.Response.Redirect ("/ Info / Detail / notfound.aspx");
}
else
{
//context.Response.Redirect(context.Request.Path);
//context.Server.Transfer(context.Request.Path);
context.RewritePath (context.Request.Path);
}
}

Server.Transfer has been tried, not good.

养狗的上帝

No exception is thrown after the request, and a blank window is returned. View the source code of the web page as follows:

<! DOCTYPE HTML PUBLIC "-// W3C // DTD HTML 4.0 Transitional // EN">
<HTML> <HEAD>
<META http-equiv = Content-Type content = "text / html; charset = gb2312"> </ HEAD>
<BODY> </ BODY> </ HTML>

mgcfox

shenmue024
   
But if *.aspx does not exist, you can still go to HttpHandler.
If it is something else, it won't work. Because *.aspx is still explained through asp.net.

Others will not work. iis. Direct report does not exist.

-------------------------------------------

Indeed, it was misled by an article.
This is quite strange.

mgcfox

You check if the file you generated is correct.
Then look at the implementation in Trace.axd.