[JIRA] Commented: (SSPCPP-425) ShibAccessControl Relative Paths to user web content

[Scott Cantor (JIRA)]

    [ https://issues.shibboleth.net/jira/browse/SSPCPP-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879#comment-13879 ] 

Scott Cantor commented on SSPCPP-425:
-------------------------------------

Unfortunately the header files for both old and new Apache suggest that the path member doesn't mean anything in any recent version, other than as a NULL/non-NULL flag that signals whether it's a virtual or physical location. That was pretty much my impression when you asked about it.

The book you're referencing is extremely out of date, BTW, that's why it's misleading.

If I have a chance, I'll run a few tests to verify whether the path is perhaps valid for htaccess files even if the header says it's not.

> ShibAccessControl Relative Paths to user web content
> ----------------------------------------------------
>
>                 Key: SSPCPP-425
>                 URL: https://issues.shibboleth.net/jira/browse/SSPCPP-425
>             Project: Shibboleth SP - C++
>          Issue Type: Improvement
>          Components: Request Processing
>         Environment: Redhat 5/6 - default packages. 
> Currently using Shibboleth SP 2.4.3
>            Reporter: aaron.roots at idp.protectnetwork.org
>            Assignee: Scott Cantor
>            Priority: Minor
>
> When using ShibAccessControl in a .htaccess file in our environment we encourage web content maintainers to place the xml file in the same location as the content they are maintaining (with a blocked file naming standard of course)
> Unfortunately this requires a full path to the location where the .htaccess file already is. This causes issues with development, testing and production environments potentially having different root file paths.
> We would like to be able to reference the .xml relatively based on the location of the .htaccess
> As discussed this could not be the default option as it would break exist config for other users
> - so just as a suggestion - maybe a new ShibAccessControlPath option - which defaults to the currently used /etc/shibboleth
> - can take a new base file path or be set to AUTO to go off the .htaccess location 
> Below are some details about how to maybe get the current location of the .htaccess file (or <Directory> path etc)
> "A cmd_parms structure is the first argument passed to all directive handlers"
> "char* path"
> "If the handler is being called to process a directive located in an access control file, 'path' will contain the path to the directory containing the .htaccess file"
> From pages 581-582 of
> http://books.google.com.au/books?id=5jAuQBe2EsMC&pg=PA448&lpg=PA448&dq=writing+apache+module+current+directory&source=bl&ots=6ZFjq9Np0j&sig=COI3gcZbCJi6jkBONnvesdyCCyM&hl=en&sa=X&ei=iCNDT5qpFtCViAef17jvBA&ved=0CEYQ6AEwBA#v=onepage&q=htaccess&f=false

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira