This is my first venture into a REST API in .NET so I expect this is just a minor issue on my part but I have a simple API that accepts 1 LNP value and returns a response. A live call is available at:

I thought however, a call to would work but it returns a 404 and I don't know why.

Is is some piece of configuration I'm missing?

Who is Participating?
Alexandre SimõesConnect With a Mentor Manager / Technology SpecialistCommented:
Hi padas...

I understand and that's why I added my second post that points directly to an MSDN blog post which is a more solid reference...
Also I believe that the full reference is useful for the question...

Anyway, answering explicitly:

Why the 404?
IIS cant resolve that URL simply because the path doesn't exist.
There's no physical resource that maps to that path.

What you need?
Something like a translations process that picks an invalid request and internally translates it to a valid one, without the user ever knowing about it.

The solution?
Create a rule in IIS that identifies a request pattern and rewrites the request pointing it to an existing resource.
This technique is called URL rewrite and is accessible as an option in your website configurations view.
In your case I think the RewriteURL setting sould be like:

Further information
A more in depth step by step explanation can be seen on the link provided here.

Alexandre SimõesManager / Technology SpecialistCommented:
Basically you want to get rid of the service name on the URL.

<< link removed by padas >>
Alexandre SimõesManager / Technology SpecialistCommented:
Scott Fell, EE MVEDeveloper & EE ModeratorCommented:
Nice answer AlexCode!
Alexandre SimõesManager / Technology SpecialistCommented:
Thanks for pulling it out of me padas! :)

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.