On Nov 11, 2013, at 3:51 PM, brainbuz <[email protected]> wrote:
> Newer versions of apache make some security changes
> so apache, even though you don't think any access control is being applied on
> the server side,
> might be blocking it by default (although that should be a 403 rather than
> 401).
>
> You could try a block like this:
>
> <Location /uri_for/my/app.fcgi>
> Order Allow,Deny
> Allow From All
> Satisfy Any
> </Location>
That did not work unfortunately... but I have found that the data I need is
available in $c->engine->env->{Authorization}, so I'll see what I can do with
that.
I'll also look at starman and see if that improves things.
Thanks,
Dan
>
> I wrote an article on deploying starman with apache in the 2011 catalyst
> advent calendar, with some errata on my blog, you might want to consider
> switching, although you would still run afoul of tighter apache defaults if
> that is indeed your problem.
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
