WCF REST URIs ending in %20 fail with 404

Question

A WCF REST web service provides a lookup in the format:

https://mysite/mycontract/search/{searchtext}

A search text of hello, or hello%20world, and the service performs correctly. However, when using text ending in whitespace as in https://mysite/mycontract/search/hello%20 the service will fail with a 404. There is no custom routing.

What limitations in wcf routing causes this, and what workarounds (ideally besides changing the uri structure) are available?

Edit w/ additional implementation info:

contract

    [ServiceContract(SessionMode = SessionMode.NotAllowed)]
    public interface IPointOfSale
    {
        .......

        [WebInvoke(UriTemplate = "search/{SKU}", Method = "GET")]
        System.Xml.Linq.XElement ProductLookup(string SKU);

    }

method

public XElement ProductLookup(string SKU)
{
   //product search here.
}

I can't reproduce this (I correctly route with %20 at the end of URL) in my WCF REST service, can you provide an example? — EkoostikMartin, Jun 20 '12 at 21:39
@EkoostikMartin I think the key is that it's not in querystring, instead at the end of the route--can you see if that effects your results? — seraphym, Jun 20 '12 at 21:55
You are correct, I modified my URI to look like yours and I got a 404 — EkoostikMartin, Jun 20 '12 at 22:12
Possibly related: http://stackoverflow.com/questions/1126735/problem-with-a-url-that-ends-with-20 — 500 - Internal Server Error, Jun 21 '12 at 01:15

score 1 · Accepted Answer · answered Aug 17 '12 at 12:31

1

I have been working with the same issue today, and found other posts telling that, in .NET 4, the solution lies in setting the following in web.config:

<httpRuntime relaxedUrlToFileSystemMapping="true" />

This solved the problem for me!

answered Aug 17 '12 at 12:31

Barslett

286
1
2
5

WCF REST URIs ending in %20 fail with 404

1 Answers1