[Typo3] CSS stylesheet hazardous LOST
jmesterh at iastate.edu
Tue Dec 20 17:01:56 CET 2005
I had a similar problem, where we were using 'config.baseURL = 1' in
the template ts. When the page cache expired, if the site was next
visited by a robot, or an odd browser that didn't send the name of
the domain in the HTTP request, the baseURL was set to either null or
some other random domain for the lifetime of that page's cache. In
the HTML template, the CSS paths were relative, so they used the
baseurl, which was junk so the CSS didn't load.
Setting config.baseURL to the domain fixed the problem.. (which was
later considered a security problem.)
On Dec 18, 2005, at 11:21 AM, Brice Bernard wrote:
> This file is static so there shouldn't be any problem, I guess?
> 2005/12/18, Michael Scharkow <mscharkow at gmx.net>:
>> Brice Bernard wrote:
>>> When I ctrl+F5 from external it works, but usual client don't
>>> know the
>>> and doesn't have to do this... But the fact is that I don't
>>> the cache is different because my hosts config file should make the
>>> the same for both internal and external side...
>>> Maybe the problem come from that I use apache mod proxy, what do you
>>> about it?
>> Yes, this is probably the problem. You should have a look at the
>> control headers sent with your css-file. Is the file static or
>> by TYPO3?
>> Typo3-english mailing list
>> Typo3-english at lists.netfielders.de
> - Brice -
> Typo3-english mailing list
> Typo3-english at lists.netfielders.de
ECpE UNIX Administrator
2101 Coover Hall, Iowa State University
Ames, IA 50011. (515) 294-7359
More information about the TYPO3-english