Access to login-restricted pages due to caching problem?

[Benno Weinzierl]

Hi,

Not logged in users can access cached pages directly (typing the url in the
browser) and get the cached output of the user who created the cache by
visiting the site. At least that is possible in my installation (latest
trunk).
If i configure the page as "not cached" this problem does not occure.
Caching Issue?

Regards, Benno


_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

[Ernesto Baschny [cron IT]]

Benno Weinzierl schrieb:

> Not logged in users can access cached pages directly (typing the url in the
> browser) and get the cached output of the user who created the cache by
> visiting the site. At least that is possible in my installation (latest
> trunk).
> If i configure the page as "not cached" this problem does not occure.
> Caching Issue?

Not in a regular installation, since the cache also considers login
conditions (group membership) so there should be two copies of the same
page in cache if the same page has different output for anoynous or not
anoymous persons, or no copy in cache if the page is not accessibly by
anonymous, thus causing an TYPO3 error.

Maybe you could provide more information on your setup? TypoScript,
page-tree, etc..

Cheers,
Ernesto
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

[Bernhard Kraft-2]

Benno Weinzierl schrieb:

> Not logged in users can access cached pages directly (typing the url in the
> browser) and get the cached output of the user who created the cache by
> visiting the site. At least that is possible in my installation (latest
> trunk).
> If i configure the page as "not cached" this problem does not occure.
> Caching Issue?

Probably your browser cached the page. Try to use another browser
(instance) when typing in the URL or clear the cache of the browser
before accessing the URL directly.

This could happen if you set the "Clear Cache Interval" flag. AFAIK
TYPO3 sends cache-headers then, which could let the browser think it
does not have to re-fetch the page as nothing has changed.


greets,
Bernhard
_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev

[Benno Weinzierl]

Sorry Guys,

it was indeed the Browsercache. I usually configure the Browser for
development to dont use cache at all.
So i didnt think of that.

Thank you,
Benno

"Bernhard Kraft" <kraftb@...> schrieb im Newsbeitrag
news:mailman.1.1255110206.21309.typo3-dev@......

> Benno Weinzierl schrieb:
>
>> Not logged in users can access cached pages directly (typing the url in
>> the
>> browser) and get the cached output of the user who created the cache by
>> visiting the site. At least that is possible in my installation (latest
>> trunk).
>> If i configure the page as "not cached" this problem does not occure.
>> Caching Issue?
>
> Probably your browser cached the page. Try to use another browser
> (instance) when typing in the URL or clear the cache of the browser
> before accessing the URL directly.
>
> This could happen if you set the "Clear Cache Interval" flag. AFAIK
> TYPO3 sends cache-headers then, which could let the browser think it
> does not have to re-fetch the page as nothing has changed.
>
>
> greets,
> Bernhard
>

_______________________________________________
TYPO3-dev mailing list
TYPO3-dev@...
http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev