From: Chris H. <ch...@ha...> - 2006-02-18 20:44:34
|
"Clemens Eisserer" asked: >> AFAIK there is nothing in any standard stopping you doing this. You generate >> it >> and you use it. >Thanks a lot for answering, great :) >> The semantics of ';'-prefixed URL parameters _other than_ 'jsessionid'are not >> constrained by any spec. that I know of . >The fears I have are that some servlet-containers maybe could treat >the prefixed part as part of the URL itself, and simply fail to resolv >the mapped servlet. Is that unlikely? Good question. The URL spec permits 'path parameters' in every component of the path e.g. /somewhere;a=14/else;b=xxx/index.html;jsessionid=123abc?name=fred is a valid URL (according to RFC 2396) with three path parameters. One would hope that _all_ servlet containers would strip this down to /somewhere/else/index.html when matching it to resources. However: 1) Form your own judgement of what Sect. 3.3 of RFC2396 is actually saying, 2) Hunt through all subsequent RFCs to see is they modify / clarify this! The problem, as I see it, is that the many subsequent RFCs related to URLs+URIs continue to let character sequences which look like path parameters be legal, but I can't find any that still retain the HTTP semantic concept of a 'path parameter'. What does worry me that the Sun Servlet spec. (I'm looking at V2.3) does not specifically say that path parameters _other than_ ones starting with 'jsessionid=' should be ignored when matching paths. Greg is on the expert group for this spec - maybe he can comment... Chris |