Asp.net WEB API : how to handle 400 bad request error when URL ends with <

Question

0.00/5 (No votes)

See more:

I am trying to handle all HTTP errors to my custom error pages, but I find that when there is a < at the end of url.
Example: http://localhost/<
Response is: Bad Request - Invalid URL HTTP Error 400. The request URL is invalid.

I want to return specific error message in this scenario.
Can anyone tell how to fix this.

Thanking You all in advance

What I have tried:

I tried to search in google not able to find the correct solution for this

Posted 17-May-16 23:19pm

ravithejag

Updated 18-May-16 3:18am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Answer 1 · 2016-05-18T03:18:00

Probably because there isn't a solution. Those requests are blocked at the kernel level, before the request even reaches IIS:
Properly handle IIS request with percent sign in url (/%)[^]
How IIS blocks characters in URLs[^]
Use of special characters like '%' '.' and ':' in an IIS URL[^]

You might be able to get the request through to IIS by changing the registry, but this will leave your server more vulnerable to attack:
Experiments in Wackiness: Allowing percents, angle-brackets, and other naughty things in the ASP.NET/IIS Request URL - Scott Hanselman[^]