If you really didn't want to do it via web.xml, which I would recommend, you probably could have a pipeline for the resource that did a <map:redirect> and took your user to a fully-qualified secure URL.

Lajos


Miles Elam wrote:
Is there a way to specify that a Cocoon resource only be accessed via a secure socket? Another way, most of the site would be Cocoon on an unencrypted channel, but you could specify that a particular URL would redirect to an https handler.

This would be an equivalent to the servlet spec that allows an entry in web.xml to say that the resource is confidential.

Is this possible now?

---

Also, do the portal/authentication frameworks use the same mechanisms as the enclosing servlet container or do they use their own, Cocoon-specific mechanisms where authentication to one has no bearing on authentication to the other?

- Miles



---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>



--
galatea.com
Cocoon training, consulting & support


---------------------------------------------------------------------
Please check that your question  has not already been answered in the
FAQ before posting.     <http://xml.apache.org/cocoon/faq/index.html>

To unsubscribe, e-mail:     <[EMAIL PROTECTED]>
For additional commands, e-mail:   <[EMAIL PROTECTED]>

Reply via email to