Jump to content

Recommended Posts

Hrmmm I've never used the domain parameter with IP addresses....

 

The domain that the cookie is available. To make the cookie available on all subdomains of example.com then you'd set it to '.example.com'. The . is not required but makes it compatible with more browsers. Setting it to www.example.com will make the cookie only available in the www subdomain. Refer to tail matching in the » spec for details.

 

So the only reason I can think of that you would need the . in front of 192.blah.blah would be if you had subdomains on your LAN IP (which isn't possible unless [ok it's not likely really, but oh well] x.x).

 

It might also be worth noting, that from the outside, cookies won't work since people from outside your LAN won't access 192.168.1.2.

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.