On 12/13/06, Tipan <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 13, 1:58 pm, "Waylan Limberg" <[EMAIL PROTECTED]> wrote:
> > On 12/13/06, Tipan <[EMAIL PROTECTED]> wrote:
> >
> > <img src="http://192.168.1.9:3000/gobites.jpg";>
> >
> > Generally speaking I believe the conventional way to do this when both
> > servers are on one machine is to point all traffic to the static
> > server (port 80) which then proxies any non-static requests on to the
> > server running Django (on some random port). That would avoid the
> > above problem.
> > ----
> > Waylan Limberg
> > [EMAIL PROTECTED]
>
> Wayne,

Who's Wayne?? ;-)

> I did have some success when I changed my ref to <img
> src="/media/gobites.jpg"> and this displays images fine, but I'm not
> convinced it's not serving them in apache as well as Django.

As the domain of your static files is different (a different port on
same ip is still considered a different host by the browser), you need
to explicitly list the domain/ip and port (if not 80) in your img
links. Seeing your not doing that (as I suggested), yeah,
apache/django is probably serving those files.

>
> What you suggest makes sense. How would I set a proxy on the static
> port - not done that before.

You would want to use mod_proxy [1]. I'v never used Lighttpd myself (I
use Apache for both) so I couldn't help with specifics, but this
example [2] might be helpful.

[1]: http://lighttpd.net/documentation/proxy.html
[2]: http://trac.lighttpd.net/trac/wiki/ApacheSubversionRecipe



-- 
----
Waylan Limberg
[EMAIL PROTECTED]

--~--~---------~--~----~------------~-------~--~----~
 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?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to