Sent from my iPhone
On Nov 11, 2013, at 9:50 PM, Dan Lowe d...@tangledhelix.com wrote:
On Nov 11, 2013, at 3:51 PM, brainbuz brain...@brainbuz.org wrote:
Newer versions of apache make some security changes
so apache, even though you don't think any access control is being applied
on
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
On Nov 11, 2013, at 3:51 PM, brainbuz brain...@brainbuz.org 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
On 9 November 2013 07:54, Dan Lowe d...@tangledhelix.com wrote:
When I move this from dev to test, which means it goes behind mod_fastcgi, it
stops working. Every request gets back 401 Unauthorized. As far as I can
tell, the Authorization header is not being passed through to Catalyst.
Has
I have begun development of a RESTful API (using Catalyst::Controller::REST),
intending to authenticate with basic HTTP authentication. Using the
myproject_server.pl debug server, everything works fine. I send the GET, an
Authorization: and an Accept: header, and I get a 200 response followed
