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 <bros...@gmail.com> 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. > >
