Yep - I'm also confused now. The original post was about cookie paths,
which are generally something you can control in application code.
Why the need for a change in the context path?
- R
On 03/11/2011 11:03 PM, Justin Edelson wrote:
That post seemed to be about cookie paths, not the context path.
Out of curiosity, under what circumstance would the context path not be / ?
Justin
On Thu, Nov 3, 2011 at 4:49 PM, broschb<[email protected]> wrote:
I posted a question on the users forum
http://old.nabble.com/ExtHttpService-cookie-path-td32768063.html#a32770708
here . The issue is that by default the context path is defined as '/' in
jetty.
Looking at the source I found that in JettyService.initilizeJetty() this is
being explicitly set. I have patched local source to load the context path
as a config using the JettyConfig class and everything works great. It
reads my config, and if not present defaults back to '/'.
I am wondering if there is anything in the spec that requires this? And if
not, what is the process to submit my change for approval, or if anyone sees
any issues with allowing this to be configurable?
-Brandon
--
View this message in context:
http://old.nabble.com/Jetty-ExtHttpService-context-path-tp32775914p32775914.html
Sent from the Apache Felix - Dev mailing list archive at Nabble.com.
--
Ascert - Taking systems to the Edge
[email protected]
+44 (0)20 7488 3470
www.ascert.com
