cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Dolg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (COCOON3-35) Support access to URLs that require authentication.
Date Mon, 25 May 2009 20:16:45 GMT

     [ https://issues.apache.org/jira/browse/COCOON3-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steven Dolg updated COCOON3-35:
-------------------------------

    Attachment: authentication2.patch

This patch adjusts all PipelineComponents to use the o.a.c.p.u.URLConnectionUtils to access
URLs.
This class will deal with authentication when accessing resources using the http protocol.

The approach is still the same: supply the user info part in the URL and authentication will
be used.


However I decided against copying the code from Excalibur and included commons-codec as an
optional dependency.

Basically this means:
* when you want/need authentication just add commons-codec to your classpath and provide the
user info.
* when you don't want/need authentication, you don't need commons-codec and must not provide
the user info.


As always, I'll wait a couple of days before applying this patch - in case there are some
issues/opinions/...

> Support access to URLs that require authentication.
> ---------------------------------------------------
>
>                 Key: COCOON3-35
>                 URL: https://issues.apache.org/jira/browse/COCOON3-35
>             Project: Cocoon 3
>          Issue Type: New Feature
>          Components: cocoon-sax, cocoon-stax, cocoon-stringtemplate
>    Affects Versions: 3.0.0-alpha-1
>            Reporter: Steven Dolg
>            Assignee: Cocoon Developers Team
>            Priority: Minor
>             Fix For: 3.0.0-alpha-2
>
>         Attachments: authentication.patch, authentication2.patch
>
>
> Currently our pipeline components cannot access URLs that require authentication.
> While it is possible to create specialized versions of each component and add authentication
there, it shouldn't be too difficult to support this feature in every pipeline component we
currently have.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message