Comments on: Using WCF for REST, Part 3 http://underground.infovark.com/2008/05/27/using-wcf-for-rest-part-3/ The Infovark technology blog Thu, 17 Nov 2011 16:06:58 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Dean http://underground.infovark.com/2008/05/27/using-wcf-for-rest-part-3/comment-page-1/#comment-59 Dean Sun, 24 Aug 2008 18:01:10 +0000 http://underground.infovark.com/?p=9#comment-59 Hi, Antonio! I'm afraid I haven't hosted WCF services from within IIS, so if that's the source of the problem, I can't be much help. The problem may be that "first.second.third.n" contains multiple dots. It's possible that the Uri classes are having trouble parsing them. Have you tried using hyphens or some other delimiter instead? Hi, Antonio! I’m afraid I haven’t hosted WCF services from within IIS, so if that’s the source of the problem, I can’t be much help.

The problem may be that “first.second.third.n” contains multiple dots. It’s possible that the Uri classes are having trouble parsing them. Have you tried using hyphens or some other delimiter instead?

]]> By: Antonio Barroso http://underground.infovark.com/2008/05/27/using-wcf-for-rest-part-3/comment-page-1/#comment-52 Antonio Barroso Fri, 22 Aug 2008 22:14:33 +0000 http://underground.infovark.com/?p=9#comment-52 Thanks for your posts about wcf and rest. I agree with the lack of flexibility of the UriTemplate. I was doing some code and after some hours of GET requests i coudn't fit in a string variable a path segment like 'http://localhost/foo.svc/first.second.third.n/' using a uritemplate like '/{myvar}'. I get a 404 not found. without the dots in the segment ('http://localhost/foo.svc/firstsecondthirdn/') i get a 200 ok and myvar=='firstsecondthirdn'. So, the dot is defining a file extension but i dont know what handler or module is doing that. Do you know where i can control this behaviour? thanks! Thanks for your posts about wcf and rest. I agree with the lack of flexibility of the UriTemplate. I was doing some code and after some hours of GET requests i coudn’t fit in a string variable a path segment like ‘http://localhost/foo.svc/first.second.third.n/‘ using a uritemplate like ‘/{myvar}’. I get a 404 not found. without the dots in the segment (‘http://localhost/foo.svc/firstsecondthirdn/‘) i get a 200 ok and myvar==’firstsecondthirdn’. So, the dot is defining a file extension but i dont know what handler or module is doing that. Do you know where i can control this behaviour? thanks!

]]> By: Vish http://underground.infovark.com/2008/05/27/using-wcf-for-rest-part-3/comment-page-1/#comment-30 Vish Wed, 28 May 2008 06:15:27 +0000 http://underground.infovark.com/?p=9#comment-30 Thanks for the feedback! I am happy that SP1 addresses some of the URI related issues. We will continue to address the pain points you mention in our next release. I have 1 question (and some rationale) about the trailing /. The URI RFC states that the trailing / is significant. One real world scenario where this is important is when documents/pages contain embedded relative links. Computing the absolute URI from the relative link will yield wrong results if the trailing / is not taken into consideration. The WCF team wanted to be compliant to the URI spec and still address the usability aspect. To that extent, if the user typed http://localhost/foo in the browser and the WCF service was listening at http://localhost/foo/ , then the WCF infrastructure would automatically send a redirect to http://localhost/foo/. Thus our hope was the user would never really notice the trailing /. Did that not work for you? Thanks Vish Thanks for the feedback! I am happy that SP1 addresses some of the URI related issues. We will continue to address the pain points you mention in our next release.

I have 1 question (and some rationale) about the trailing /. The URI RFC states that the trailing / is significant. One real world scenario where this is important is when documents/pages contain embedded relative links. Computing the absolute URI from the relative link will yield wrong results if the trailing / is not taken into consideration.

The WCF team wanted to be compliant to the URI spec and still address the usability aspect. To that extent, if the user typed http://localhost/foo in the browser and the WCF service was listening at http://localhost/foo/ , then the WCF infrastructure would automatically send a redirect to http://localhost/foo/. Thus our hope was the user would never really notice the trailing /.

Did that not work for you?

Thanks
Vish

]]>