M
matt
You cannot map a blank extension to be run by asp.net (i.e in your
httpmodule), so the only way I have found to manage this is to create a
custom 404 page which checks if the 404 is caused by the situation you
describe (in its simplest form just checking if the request ends with
..aspx), you can then redirect to the appropriate page using a
Response.Redirect.
As far as I know this really is the only way around this problem,
although I am aware it isn't the most elegant it does solve the problem.
HTH
Matt
httpmodule), so the only way I have found to manage this is to create a
custom 404 page which checks if the 404 is caused by the situation you
describe (in its simplest form just checking if the request ends with
..aspx), you can then redirect to the appropriate page using a
Response.Redirect.
As far as I know this really is the only way around this problem,
although I am aware it isn't the most elegant it does solve the problem.
HTH
Matt