|
Clean room implementation of org.mortbay.jetty.securtiy.HTAccessHandler
----------------------------------------------------------------------- Key: JETTY-962 URL: http://jira.codehaus.org/browse/JETTY-962 Project: Jetty Issue Type: Task Affects Versions: 7.0.0.pre5 Reporter: Greg Wilkins We need to replace the HTAccessHandler with a clean room implementation for the move to org.eclipse due to lack of CLAs and different copyrights. The implementation should be clean room - ie please don't look at the existing source code (ie so I can't do this). The simplest thing would be if new contribution had copyright to mortbay (as most other source is) and a normal Jetty CLA signed. Alternately the auther needs to sign a new eclipse ready CLA... which I'm not sure we have ready to sign yet. The handler should implement a SecurityHandler that uses apache .htaccess files to control access. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
[ http://jira.codehaus.org/browse/JETTY-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Wilkins reassigned JETTY-962: ---------------------------------- Assignee: David Yu Can you put this on your todo list > Clean room implementation of org.mortbay.jetty.securtiy.HTAccessHandler > ----------------------------------------------------------------------- > > Key: JETTY-962 > URL: http://jira.codehaus.org/browse/JETTY-962 > Project: Jetty > Issue Type: Task > Affects Versions: 7.0.0.pre5 > Reporter: Greg Wilkins > Assignee: David Yu > > We need to replace the HTAccessHandler with a clean room implementation for the move to org.eclipse due to > lack of CLAs and different copyrights. > The implementation should be clean room - ie please don't look at the existing source code (ie so I can't do this). The simplest thing would be if new contribution had copyright to mortbay (as most other source is) and a normal Jetty CLA signed. Alternately the auther needs to sign a new eclipse ready CLA... which I'm not sure we have ready to sign yet. > The handler should implement a SecurityHandler that uses apache .htaccess files to control access. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
In reply to this post by JIRA jira@codehaus.org
[ http://jira.codehaus.org/browse/JETTY-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Gorovoy reassigned JETTY-962: ------------------------------------- Assignee: Michael Gorovoy > Clean room implementation of org.mortbay.jetty.securtiy.HTAccessHandler > ----------------------------------------------------------------------- > > Key: JETTY-962 > URL: http://jira.codehaus.org/browse/JETTY-962 > Project: Jetty > Issue Type: Task > Affects Versions: 7.0.0.pre5 > Reporter: Greg Wilkins > Assignee: Michael Gorovoy > > We need to replace the HTAccessHandler with a clean room implementation for the move to org.eclipse due to > lack of CLAs and different copyrights. > The implementation should be clean room - ie please don't look at the existing source code (ie so I can't do this). The simplest thing would be if new contribution had copyright to mortbay (as most other source is) and a normal Jetty CLA signed. Alternately the auther needs to sign a new eclipse ready CLA... which I'm not sure we have ready to sign yet. > The handler should implement a SecurityHandler that uses apache .htaccess files to control access. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
In reply to this post by JIRA jira@codehaus.org
[ https://jira.codehaus.org/browse/JETTY-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Wilkins closed JETTY-962. ------------------------------ Resolution: Won't Fix Assignee: (was: Michael Gorovoy) No demand > Clean room implementation of org.mortbay.jetty.securtiy.HTAccessHandler > ----------------------------------------------------------------------- > > Key: JETTY-962 > URL: https://jira.codehaus.org/browse/JETTY-962 > Project: Jetty > Issue Type: Task > Affects Versions: 7.0.0.pre5 > Reporter: Greg Wilkins > > We need to replace the HTAccessHandler with a clean room implementation for the move to org.eclipse due to > lack of CLAs and different copyrights. > The implementation should be clean room - ie please don't look at the existing source code (ie so I can't do this). The simplest thing would be if new contribution had copyright to mortbay (as most other source is) and a normal Jetty CLA signed. Alternately the auther needs to sign a new eclipse ready CLA... which I'm not sure we have ready to sign yet. > The handler should implement a SecurityHandler that uses apache .htaccess files to control access. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
| Powered by Nabble | Edit this page |
