I considered this before, but with the configuration of the lan of my client if I try to access the public IP from a machine of the lan I get the router's configuration web page. And they don't allow me to reconfigure this.
It's important to get the site from both sides because they will use the backed of the aplication, the admin site, from the office. Thanks in any way Jeremy ;) I must say that this is a really active mailing list, I always find anybody who tries to help me. Goyo Jeremy Osterhouse wrote: > [EMAIL PROTECTED] wrote: > > > As we haven't a domain name I set the SESSION_COOKIE_DOMAIN to the > > public IP of the site. Well this works great from Internet, but when I > > try to access the admin site from the lan of my client I couldn't log > > in. If I change the SESSION_COOKIE_DOMAIN it works into the lan but not > > outside. It's not a browser > > related problem because I tested this with at least two different > > browsers IE and Firefox. > > If I understand what you're saying, the easiest solution would be to > simply always access the site using the public IP, whether you're on > the lan or not. If it's important to you be able to get to the site > from either the public IP or the internal IP, I imagine it wouldn't be > too hard to modify django.contrib.sessions.middleware to set the > cookie's host to the correct IP. > > -Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
