No, nothing to do with HTTP_HOST, that comes from the server.
The point of the sites framework is to differentiate between different
sites, so a * site would be pointless.
If I were you I'd sort out my templates so that instead of
/some/media/location/css/styles.css
you have
{{MEDIA_URL}}/css/styles.css
and instead of
img src="/some/media/location/{{model.image}}"
you have
img src="{{model.image.url}}}"
then you just have to change your MEDIA_URL setting and you're almost
there.
Kip.
On Sep 16, 2:46 pm, est <[EMAIL PROTECTED]> wrote:
> Thank you Kip.
>
> Call me stupid but does site framework have something to do with HTTP
> HOST header?
>
> But in my case the site is for ANYSITE, no matter you visit the site
> by IP, domain, or even customized CNAME you cann visit the site with
> out any problem (Why there isn't a wildcard * in site framework?)
>
> I will looking into TEMPLATE_CONTEXT_PROCESSORS thought, maybe a
> customized filter would help
>
> :-)
>
> On Sep 16, 8:01 pm, Kip Parker <[EMAIL PROTECTED]> wrote:
>
> > > no, it's not THAT simple.
>
> > It really is that simple, honest, but your brain has made it all
> > complicated. Look athttp://docs.djangoproject.com/en/dev/ref/contrib/sites/
> > (sites framework), TEMPLATE_CONTEXT_PROCESSORS setting and
> > RequestContext and the URL dispatcher docs, the answers to your
> > problem and many more besides are in there.
>
> > One tip, most people use MEDIA_URL in their templates a lot.
>
> > Kip.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
