How do I handle wrongly suffixed url of webpages?
-
How do I handle wrongly suffixed url of webpages? for eg: Correct url:
http://mdc01c/en/Journey/Played with url:http://mdc01c/en/Journey/dfhow to handle 'Played with url' case in ASP.Net? Please guide. Thanks.// ♫ 99 little bugs in the code, // 99 bugs in the code // We fix a bug, compile it again // 101 little bugs in the code ♫
Tell your manager, while you code: "good, cheap or fast: pick two. "
-
How do I handle wrongly suffixed url of webpages? for eg: Correct url:
http://mdc01c/en/Journey/Played with url:http://mdc01c/en/Journey/dfhow to handle 'Played with url' case in ASP.Net? Please guide. Thanks.// ♫ 99 little bugs in the code, // 99 bugs in the code // We fix a bug, compile it again // 101 little bugs in the code ♫
Tell your manager, while you code: "good, cheap or fast: pick two. "
Ravi Sant wrote:
how to handle 'Played with url' case in ASP.Net?
Display a 404-page? What else would you want to do? You could log the IP from the requestor, and block them for a certain period if you're under the impression that they're looking for holes in your security.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
Ravi Sant wrote:
how to handle 'Played with url' case in ASP.Net?
Display a 404-page? What else would you want to do? You could log the IP from the requestor, and block them for a certain period if you're under the impression that they're looking for holes in your security.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
I am sorry, if have wrongly or partially framed question. I have already done that using customerrors=on in asp.net web.config. But, it does not works for internal websites and I am to no-where since yesterday.
// ♫ 99 little bugs in the code, // 99 bugs in the code // We fix a bug, compile it again // 101 little bugs in the code ♫
Tell your manager, while you code: "good, cheap or fast: pick two. "
-
Ravi Sant wrote:
how to handle 'Played with url' case in ASP.Net?
Display a 404-page? What else would you want to do? You could log the IP from the requestor, and block them for a certain period if you're under the impression that they're looking for holes in your security.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]