Re: Django development running on 127.0.0.1:8000 not accessible from same machine

Hi Jirka,

That does not seem to be the case. I set rhe proxy server settings to no
proxy and it still prepends a www in front of the IP address. I could
investigate this further but I am little pressed for time at present.

Thanks,
nav

On Tuesday 28 August 2012 10:39 AM, jirka.vejrazka@gmail.com wrote:
> Hi nav,
>
> A long shot - do you happen to have a proxy defined in your browser? It is possible to define a proxy for *all* request (including localhost) - this would have the same effect.
>
> HTH
>
> Jirka
> -----Original Message-----
> From: nav <navanitachora@gmail.com>
> Sender: django-users@googlegroups.com
> Date: Mon, 27 Aug 2012 21:00:12
> To: Django users<django-users@googlegroups.com>
> Reply-To: django-users@googlegroups.com
> Subject: Re: Django development running on 127.0.0.1:8000 not accessible from
> same machine
>
> Hi Anton,
>
> Thank you for your email.
>
> I have tried all of the methods you had suggested but to no avail.
>
> In all my years of Django development the localhost address has worked
> flawlessly. I have also tried with multiple Django projects and other
> Linux installations and the problem persists. This makes me think this
> is a DNS issue that may be due to a network related problem. In which
> case I will have to investigate. I will post once I find a work around
> or solution.
>
> Cheers,
> nav
>
> On Aug 27, 5:36 pm, Anton Baklanov <antonbakla...@gmail.com> wrote:
>> oh, i misunderstood your question.
>>
>> try to type url with schema into browser's address bar. i mean, use 'http://localhost:8000/'instead of 'localhost:8000'.
>> also it's possible that some browser extension does this, try disabling
>> them all.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Aug 27, 2012 at 10:53 AM, nav <navanitach...@gmail.com> wrote:
>>> Dear Folks,
>>
>>> I am running my django development server on 127.0.0.1:8000 and accessing
>>> this address from my web browser on the same machine. In the past few days
>>> I have found thet the web browsers keep prepending the address with "www."
>>> when using the above address. 127.0.0.1 without the prot number works fine
>>> but the django development server requires a port number.
>>
>>> I have not encountered this problem before and am puzzled by what is
>>> happening. I am working on a Kubuntu 12.04 linux box and my /etc/hosts/
>>> file is below if that helps:
>>
>>> ====================
>>> 127.0.0.1 localhost
>>> 127.0.1.1 <mymachinename>
>>
>>> # The following lines are desirable for IPv6 capable hosts
>>> ::1 ip6-localhost ip6-loopback
>>> fe00::0 ip6-localnet
>>> ff00::0 ip6-mcastprefix
>>> ff02::1 ip6-allnodes
>>> ff02::2 ip6-allrouters
>>> ====================
>>
>>> TIA
>>> Cheers,
>>> nav
>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Django users" group.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msg/django-users/-/EZzlz6iQOGoJ.> To post to this group, send email todjango-users@googlegroups.com.
>>> To unsubscribe from this group, send email to>django-users+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/django-users?hl=en.
>>
>> --
>> Regards,
>> Anton Baklanov
>

--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.