If you have a front end web server then you can let it handle the CORS for
you and don't worry about it in your app, I've used the approach in
https://awesometoast.com/cors/ with success for apache, I've heard it's
also pretty straightforward for nginx. This way you avoid a full catalyst
request
On Thu Nov 13 2014 at 20:22:51 Aristotle Pagaltzis pagalt...@gmx.de wrote:
Hi Adam,
* Adam Witney awit...@sgul.ac.uk [2014-11-13 12:45]:
I saw this post, but I 'm not sure I can use it to get the Catalyst
normal startup output in my logs. Is this possible?
The problem with redirecting
On Thu, Apr 16, 2009 at 5:47 PM, Scott Thomson smoothho...@gmail.com wrote:
On Tue, Apr 14, 2009 at 7:50 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 14 Apr 2009, at 10:58, Scott Thomson wrote:
Currently Catalyst::Plugin::Session::State::Cookie doesn't allow
configuration of the HttpOnly
On Tue, Apr 14, 2009 at 7:50 PM, Tomas Doran bobtf...@bobtfish.net wrote:
On 14 Apr 2009, at 10:58, Scott Thomson wrote:
Currently Catalyst::Plugin::Session::State::Cookie doesn't allow
configuration of the HttpOnly flag, it looks trivial to add, so
basically I'm wondering whether this idea
Hi,
Currently Catalyst::Plugin::Session::State::Cookie doesn't allow
configuration of the HttpOnly flag, it looks trivial to add, so
basically I'm wondering whether this idea has been discussed and
discounted before and if there is any reason why I shouldn't just
patch it?
Cheers
