Hi, I'd like to server two separate domains from the same code-base and even the same process. Currently I set the cookie_domain in the configuration file, but that will not be good once there are two domains. Is it possible to set the cookie_domain on the fly in the code? This is what I have now: engines: session: YAML: cookie_domain: ".example.com" regards Gabor
On Sat, 2016-03-05 at 16:43 +0200, Gabor Szabo wrote:
Hi,
I'd like to server two separate domains from the same code-base and even the same process.
Is this related at all? https://github.com/PerlDancer/Dancer2/issues/1035 One suggestion I was given was to use Dancer2::Session::Cookie, which is certainly an option for me, but I haven't explored it further. Andy
On Sat, Mar 5, 2016 at 4:59 PM, Andrew Beverley <andy@andybev.com> wrote:
On Sat, 2016-03-05 at 16:43 +0200, Gabor Szabo wrote:
Hi,
I'd like to server two separate domains from the same code-base and even the same process.
Is this related at all?
https://github.com/PerlDancer/Dancer2/issues/1035
One suggestion I was given was to use Dancer2::Session::Cookie, which is certainly an option for me, but I haven't explored it further.
Andy
That seems to be the same case. I tried Dancer2::Session::Cookie and it seems to work, but so far I could not convince it to store the session in the server. As I can see it stores everything in the cookie itself. Gabor
On Sun, Mar 6, 2016 at 8:43 PM, Gabor Szabo <gabor@szabgab.com> wrote:
On Sat, Mar 5, 2016 at 4:59 PM, Andrew Beverley <andy@andybev.com> wrote:
On Sat, 2016-03-05 at 16:43 +0200, Gabor Szabo wrote:
Hi,
I'd like to server two separate domains from the same code-base and even the same process.
Is this related at all?
https://github.com/PerlDancer/Dancer2/issues/1035
One suggestion I was given was to use Dancer2::Session::Cookie, which is certainly an option for me, but I haven't explored it further.
Andy
That seems to be the same case.
I tried Dancer2::Session::Cookie and it seems to work, but so far I could not convince it to store the session in the server. As I can see it stores everything in the cookie itself.
Dancer2::Session::Cookie explicitly saves it in the cookie - that's why it's called "Cookie". It won't save it on the server. This is not a bug, this is the exact intention of the module.
On Tue, Mar 8, 2016 at 10:42 AM, Sawyer X <xsawyerx@gmail.com> wrote:
On Sun, Mar 6, 2016 at 8:43 PM, Gabor Szabo <gabor@szabgab.com> wrote:
I tried Dancer2::Session::Cookie and it seems to work, but so far I could not convince it to store the session in the server. As I can see it stores everything in the cookie itself.
Dancer2::Session::Cookie explicitly saves it in the cookie - that's why it's called "Cookie". It won't save it on the server.
This is not a bug, this is the exact intention of the module.
Yes. These days I am a bit slower than usual on comprehension. Gabor
participants (3)
-
Andrew Beverley -
Gabor Szabo -
Sawyer X