[jira] [Commented] (FELIX-3198) Support generic configuration properties
[ https://issues.apache.org/jira/browse/FELIX-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143786#comment-13143786 ] Rob Walker commented on FELIX-3198: --- I guess my one concern here is whether the model for these is standard in terms of the OSGi spec, or at least common to the approach other containers take in this area. Is there also a case where different servlets may want to be able to have different servlet context paths - either per servlet, or perhaps per ServletContext used when registering their aliases. > Support generic configuration properties > > > Key: FELIX-3198 > URL: https://issues.apache.org/jira/browse/FELIX-3198 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.2.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.2.2 > > > Currently the Jetty configuration only allows for a hard-coded limited sets > of properties provided in either the Configuration Admin configuration or as > framework properties. > Adding support for generic properties allows administrators to configure the > Servlet Container more specifically. Examples of such properties would be > Jetty specific session configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jetty ExtHttpService context path
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 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 r...@ascert.com +44 (0)20 7488 3470 www.ascert.com
[jira] [Resolved] (FELIX-3200) Track PID changes of ManagedService[Factory] services
[ https://issues.apache.org/jira/browse/FELIX-3200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-3200. -- Resolution: Fixed Fix Version/s: configadmin-1.4.0 Tracking these service.pid changes now by keeping record of service.pid value after registration and after each registration modification. If a registration modification causes no changes in the registered service PIDs (we ignore the order of pids in the array for now) nothing happens. Otherwise the ManagedService.update or ManagedServiceFactory.update method is called for each of the new service pid values. Implemented in Rev. 1197348 > Track PID changes of ManagedService[Factory] services > - > > Key: FELIX-3200 > URL: https://issues.apache.org/jira/browse/FELIX-3200 > Project: Felix > Issue Type: Task > Components: Configuration Admin >Affects Versions: configadmin-1.2.8 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: configadmin-1.4.0 > > > Configuration Admin 1.4 requires implementations to track service.pid changes > of registered ManagedService and ManagedServiceFactory services: > > The Configuration Admin must track the configuration targets on their actual > > PID. That is, if the service.pid service property is modied then the > > Configuration Admin must treat it as if the service was unregistered and > > then > > re-registered with the new PID. > This means we have to track service registration PIDs and compare them > against any service registration changes and appropriately update the > services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3200) Track PID changes of ManagedService[Factory] services
Track PID changes of ManagedService[Factory] services - Key: FELIX-3200 URL: https://issues.apache.org/jira/browse/FELIX-3200 Project: Felix Issue Type: Task Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Felix Meschberger Assignee: Felix Meschberger Configuration Admin 1.4 requires implementations to track service.pid changes of registered ManagedService and ManagedServiceFactory services: > The Configuration Admin must track the configuration targets on their actual > PID. That is, if the service.pid service property is modied then the > Configuration Admin must treat it as if the service was unregistered and then > re-registered with the new PID. This means we have to track service registration PIDs and compare them against any service registration changes and appropriately update the services. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Jetty ExtHttpService context path
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 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. > >
Jetty ExtHttpService context path
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.
[jira] [Resolved] (FELIX-3196) Security Problem: Getting full file access within the cache directory from one Bundle
[ https://issues.apache.org/jira/browse/FELIX-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls resolved FELIX-3196. --- Resolution: Fixed Fix Version/s: framework.security-2.2.0 I confirm that there is a bug. I commited a fix to trunk and pushed a new snapshot. Please close this issue if it works for you. > Security Problem: Getting full file access within the cache directory from > one Bundle > - > > Key: FELIX-3196 > URL: https://issues.apache.org/jira/browse/FELIX-3196 > Project: Felix > Issue Type: Bug > Components: Framework Security >Affects Versions: framework.security-2.0.0 > Environment: felix-framework-4.0.1 >Reporter: Michael Grammling >Assignee: Karl Pauls > Fix For: framework.security-2.2.0 > > > It seems that there is a security problem in the "Framework Security" module > of Felix. > I have full access to the bundle cache directory from each bundle. > Expectation: I should only get full access to the data storage of the bundle > itself. > Actually I was able to create files from Bundle 25 inside the data storage of > Bundle 0. > I even could delete the whole directory of Bundle 0. > I checked the same with Knopflerfish which does this check correctly. > Do I have to set more configuration parameters? > The OSGi specification defines that the framework should grant access to the > bundle's data storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FELIX-3196) Security Problem: Getting full file access within the cache directory from one Bundle
[ https://issues.apache.org/jira/browse/FELIX-3196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Pauls reassigned FELIX-3196: - Assignee: Karl Pauls > Security Problem: Getting full file access within the cache directory from > one Bundle > - > > Key: FELIX-3196 > URL: https://issues.apache.org/jira/browse/FELIX-3196 > Project: Felix > Issue Type: Bug > Components: Framework Security >Affects Versions: framework.security-2.0.0 > Environment: felix-framework-4.0.1 >Reporter: Michael Grammling >Assignee: Karl Pauls > > It seems that there is a security problem in the "Framework Security" module > of Felix. > I have full access to the bundle cache directory from each bundle. > Expectation: I should only get full access to the data storage of the bundle > itself. > Actually I was able to create files from Bundle 25 inside the data storage of > Bundle 0. > I even could delete the whole directory of Bundle 0. > I checked the same with Knopflerfish which does this check correctly. > Do I have to set more configuration parameters? > The OSGi specification defines that the framework should grant access to the > bundle's data storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3162) Allow configuration of headerBufferSize in Jetty
[ https://issues.apache.org/jira/browse/FELIX-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-3162. -- Resolution: Fixed Fix Version/s: http-2.2.2 Added three configuration parameters in Rev. 1197051 and update the doc. page. The properties are: * org.apache.felix.http.jetty.headerBufferSize * org.apache.felix.http.jetty.requestBufferSize * org.apache.felix.http.jetty.responseBufferSize > Allow configuration of headerBufferSize in Jetty > > > Key: FELIX-3162 > URL: https://issues.apache.org/jira/browse/FELIX-3162 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Jukka Zitting >Assignee: Felix Meschberger >Priority: Minor > Fix For: http-2.2.2 > > > It would be nice if the headerBufferSize option [1] in Jetty could be set as > an OSGi configuration property. > [1] http://docs.codehaus.org/display/JETTY/Configuring+Connectors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-2687) Make HTTP connection timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-2687. -- Resolution: Fixed Fix Version/s: http-2.2.2 Patch applied to new HTTP Service only. The old http.jetty project has been removed as of FELIX-3044 already so nothing to be applied there. > Make HTTP connection timeout configurable > - > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Fix For: http-2.2.2 > > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-2687) Make HTTP connection timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142998#comment-13142998 ] Felix Meschberger commented on FELIX-2687: -- Committed the patch to the new HTTP service project in Rev. 1197027 and updated the doc. page. > Make HTTP connection timeout configurable > - > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3199) Allow configuration of Session timeout
[ https://issues.apache.org/jira/browse/FELIX-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-3199. -- Resolution: Fixed Fix Version/s: http-2.2.2 Implemented support for the property in Rev. 1197019 and updated the doc. page. > Allow configuration of Session timeout > -- > > Key: FELIX-3199 > URL: https://issues.apache.org/jira/browse/FELIX-3199 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.2.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.2.2 > > > Currently the Jetty based implementation does not allow the configuration of > the HTTP Session life time and thus keeps the Jetty default of "forever". > Propose the addition of a configuration property > "org.apache.felix.http.session.timeout" which follows the semantics of the > session-timeout element of the web application descriptor. Like for the web > application descriptor this value is specified in minutes (whereas Jetty > would allow for seconds). Choosing minutes should follow the rule of least > surprise. > See also this comment on FELIX-2687: > https://issues.apache.org/jira/browse/FELIX-2687?focusedCommentId=13122559&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13122559 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3197) Add support to configure the interface to listen on
[ https://issues.apache.org/jira/browse/FELIX-3197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-3197. -- Resolution: Fixed Fix Version/s: http-2.2.2 Implemented support for this property in Rev. 1197013 and updated the doc. page. > Add support to configure the interface to listen on > --- > > Key: FELIX-3197 > URL: https://issues.apache.org/jira/browse/FELIX-3197 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.2.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.2.2 > > > Currently the Http Service implementation only allows to configure the port > on which the HTTP or HTTPS connector is listening. For full flexibility it > must be possible to also provide information on which interface(s) to listen > on. > To this avail a new string typed configuration property > "org.apache.felix.host" should be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (FELIX-3198) Support generic configuration properties
[ https://issues.apache.org/jira/browse/FELIX-3198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-3198. -- Resolution: Fixed Fix Version/s: http-2.2.2 Added support for generic properties in Rev. 1196998 Also implemented generic Jetty Session configuration based on this functionality for the following properties: * Name of the Session cookie: org.mortbay.jetty.servlet.SessionCookie (default: JSESSIONID) * Name of the Session Request parameter: org.mortbay.jetty.servlet.SessionURL (default: jsessionid") * Domain for the session cookie: org.mortbay.jetty.servlet.SessionDomain (default: null) * Path for the session cookie: org.mortbay.jetty.servlet.SessionPath (default: Servlet Context Path) * Max age value for the session cookie: org.mortbay.jetty.servlet.MaxAge (default: -1) (updated the doc page for these additions) > Support generic configuration properties > > > Key: FELIX-3198 > URL: https://issues.apache.org/jira/browse/FELIX-3198 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.2.0 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.2.2 > > > Currently the Jetty configuration only allows for a hard-coded limited sets > of properties provided in either the Configuration Admin configuration or as > framework properties. > Adding support for generic properties allows administrators to configure the > Servlet Container more specifically. Examples of such properties would be > Jetty specific session configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-2803) Separate project versions from each other
[ https://issues.apache.org/jira/browse/FELIX-2803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142957#comment-13142957 ] Felix Meschberger commented on FELIX-2803: -- Detached the Jetty sub project in Rev. 1196993 to only depend on released dependencies (parent, API, and base) for now. > Separate project versions from each other > - > > Key: FELIX-2803 > URL: https://issues.apache.org/jira/browse/FELIX-2803 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.2.0 >Reporter: Felix Meschberger > Fix For: http-2.2.2 > > > Currently the versions of the Http Service bundles are linked to each other > by way of inheriting the project version number from the parent project. This > results in the implied requirement to always relase all bundles in one go. > IMHO this is not very ideal because there are some bundles, which will have > more releases (for example http.base) and some bundles which will have close > to no releases (e.g. http.api). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-2687) Make HTTP connection timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-2687: - Summary: Make HTTP connection timeout configurable (was: Make HTTP session timeout configurable) > Make HTTP connection timeout configurable > - > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-2687) Make HTTP session timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142954#comment-13142954 ] Felix Meschberger commented on FELIX-2687: -- We have to make sure to not mix issues here: One is the HTTP(s) connection timeout of the original request. The other is the session timeout, which is an equally important issues. This shall be handled in FELIX-3199 > Make HTTP session timeout configurable > -- > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3199) Allow configuration of Session timeout
Allow configuration of Session timeout -- Key: FELIX-3199 URL: https://issues.apache.org/jira/browse/FELIX-3199 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Currently the Jetty based implementation does not allow the configuration of the HTTP Session life time and thus keeps the Jetty default of "forever". Propose the addition of a configuration property "org.apache.felix.http.session.timeout" which follows the semantics of the session-timeout element of the web application descriptor. Like for the web application descriptor this value is specified in minutes (whereas Jetty would allow for seconds). Choosing minutes should follow the rule of least surprise. See also this comment on FELIX-2687: https://issues.apache.org/jira/browse/FELIX-2687?focusedCommentId=13122559&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13122559 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-2687) Make HTTP session timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-2687: - Comment: was deleted (was: Dear Sender / Guten Tag / Bonjour Thank you for your message. As of October 1st 2011, I am no longer working at ETH Zurich. Please contact Olaf A. Schulte for further information. I can be reached at tob...@entwinemedia.com instead or privately at tob...@wunden.net. Danke für Ihre Nachricht. Seit dem 1. Oktober 2011 arbeite ich nicht mehr an der ETH Zürich. Bitte wenden Sie sich stattdessen an Olaf A. Schulte . Zukünftig bin ich unter tob...@entwinemedia.com oder privat unter tob...@wunden.net erreichbar. Regards / Mit freundlichen Grüssen / Cordialement T. Wunden -- ETH Zürich, Tobias Wunden, ID-MMS Rämistrasse 101, 8092 Zürich Tel. +41 44 633 73 21 tobias.wun...@id.ethz.ch http://www.mms.ethz.ch ) > Make HTTP session timeout configurable > -- > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3198) Support generic configuration properties
Support generic configuration properties Key: FELIX-3198 URL: https://issues.apache.org/jira/browse/FELIX-3198 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Currently the Jetty configuration only allows for a hard-coded limited sets of properties provided in either the Configuration Admin configuration or as framework properties. Adding support for generic properties allows administrators to configure the Servlet Container more specifically. Examples of such properties would be Jetty specific session configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3197) Add support to configure the interface to listen on
Add support to configure the interface to listen on --- Key: FELIX-3197 URL: https://issues.apache.org/jira/browse/FELIX-3197 Project: Felix Issue Type: Improvement Components: HTTP Service Affects Versions: http-2.2.0 Reporter: Felix Meschberger Assignee: Felix Meschberger Currently the Http Service implementation only allows to configure the port on which the HTTP or HTTPS connector is listening. For full flexibility it must be possible to also provide information on which interface(s) to listen on. To this avail a new string typed configuration property "org.apache.felix.host" should be added. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FELIX-3196) Security Problem: Getting full file access within the cache directory from one Bundle
Security Problem: Getting full file access within the cache directory from one Bundle - Key: FELIX-3196 URL: https://issues.apache.org/jira/browse/FELIX-3196 Project: Felix Issue Type: Bug Components: Framework Security Affects Versions: framework.security-2.0.0 Environment: felix-framework-4.0.1 Reporter: Michael Grammling It seems that there is a security problem in the "Framework Security" module of Felix. I have full access to the bundle cache directory from each bundle. Expectation: I should only get full access to the data storage of the bundle itself. Actually I was able to create files from Bundle 25 inside the data storage of Bundle 0. I even could delete the whole directory of Bundle 0. I checked the same with Knopflerfish which does this check correctly. Do I have to set more configuration parameters? The OSGi specification defines that the framework should grant access to the bundle's data storage. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FELIX-2687) Make HTTP session timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13142935#comment-13142935 ] Tobias Wunden commented on FELIX-2687: -- Dear Sender / Guten Tag / Bonjour Thank you for your message. As of October 1st 2011, I am no longer working at ETH Zurich. Please contact Olaf A. Schulte for further information. I can be reached at tob...@entwinemedia.com instead or privately at tob...@wunden.net. Danke für Ihre Nachricht. Seit dem 1. Oktober 2011 arbeite ich nicht mehr an der ETH Zürich. Bitte wenden Sie sich stattdessen an Olaf A. Schulte . Zukünftig bin ich unter tob...@entwinemedia.com oder privat unter tob...@wunden.net erreichbar. Regards / Mit freundlichen Grüssen / Cordialement T. Wunden -- ETH Zürich, Tobias Wunden, ID-MMS Rämistrasse 101, 8092 Zürich Tel. +41 44 633 73 21 tobias.wun...@id.ethz.ch http://www.mms.ethz.ch > Make HTTP session timeout configurable > -- > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FELIX-2687) Make HTTP session timeout configurable
[ https://issues.apache.org/jira/browse/FELIX-2687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-2687: Assignee: Felix Meschberger > Make HTTP session timeout configurable > -- > > Key: FELIX-2687 > URL: https://issues.apache.org/jira/browse/FELIX-2687 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 > Environment: apache-karaf-2.1.0 on openjdk-6b18/Linux >Reporter: Wolfgang Glas >Assignee: Felix Meschberger > Attachments: configurable-http-timeout.patch > > > Hi all, > ThX very much for the really smooth http service packaging ;-) > According to the docs and to my code review there is no possibility to > configure the HTTP session timeout in felix' HTTP service bundle. > It would be very much appreciated, if such a possiblity might be introduced > in a future version of HTTP service. >TIA and best regards, > Wolfgang Glas -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (FELIX-3162) Allow configuration of headerBufferSize in Jetty
[ https://issues.apache.org/jira/browse/FELIX-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-3162: Assignee: Felix Meschberger > Allow configuration of headerBufferSize in Jetty > > > Key: FELIX-3162 > URL: https://issues.apache.org/jira/browse/FELIX-3162 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Reporter: Jukka Zitting >Assignee: Felix Meschberger >Priority: Minor > > It would be nice if the headerBufferSize option [1] in Jetty could be set as > an OSGi configuration property. > [1] http://docs.codehaus.org/display/JETTY/Configuring+Connectors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
