You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "David Vittor (JIRA)" <ji...@apache.org> on 2015/03/06 23:41:38 UTC

[jira] [Commented] (JSPWIKI-877) Allow jspwiki.properties filterConfig and policy.file to have fully qualified paths

    [ https://issues.apache.org/jira/browse/JSPWIKI-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14351056#comment-14351056 ] 

David Vittor commented on JSPWIKI-877:
--------------------------------------

Need to verify against JSPWIKI-878 before finishing these changes, as I think these will conflict. But happy to merge these together.

> Allow jspwiki.properties filterConfig and policy.file to have fully qualified paths
> -----------------------------------------------------------------------------------
>
>                 Key: JSPWIKI-877
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-877
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Core & storage
>    Affects Versions: 2.10.1
>            Reporter: David Vittor
>            Assignee: David Vittor
>         Attachments: JSPWIKI-877.patch
>
>
> Currently adding the following properties does not work:
> * jspwiki.policy.file=C:/temp/jspwiki-custom.policy
> * jspwiki.filterConfig=C:/temp/jspwiki-filters.xml
> The policy file only checks certain locations, and not fully qualified paths.
> The filterConfig has the same problem, but does work in linux, but not in windows as this expects a URL, e.g. file:/C:/temp/... but this causes a SEVERE filterStart error in tomcat.
> Note: These seem to be inconsistant with UserDatabase and GroupDatabase



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)