TYPO3 Core

I can confirm this issue.
The admin-panel reports an cHash problem.
This is the output of the admin-panel if default action (list) is called without extbase parameters (from the menu):
The incoming cHash "ede237831fbbae721d30bffc4e44dcfa" and calculated cHash "ae541f40806fc69f595681cafa31473f" did not match, so caching was disabled. The fieldlist used was "encryptionKey"

If the same action is called within the extension the fieldlist contains all parameters but calculating fails also:
The incoming cHash "8a4628d52782ffecd2be2c0de843b193" and calculated cHash "25e2a1a436ba9e59ee7b05fcada244d3" did not match, so caching was disabled. The fieldlist used was "encryptionKey,tx_extension_plugin[action],tx_extension_plugin[controller],tx_extension_plugin[model]"

I don't know why the model is part of the fieldlist in the list action.

It looks like there goes something wrong with the fields for the calculation.

In my show action the caching works fine.

What do you mean with "RealURL cHash parameters"?
I have set

'enableCHashCache' => true,

may it is a problem with the

'defaultToHTMLsuffixOnPrev' => true,

I can confirm this issue too.

There are two reasons why pages are not cached:
- Setting 'defaultToHTMLsuffixOnPrev' to something else than the default value
- Using optional parameters in the URL

A partly working workaround is to use "fixedPostVars" instead of "postVarSets" like:

$TYPO3_CONF_VARS['EXTCONF']['realurl']['_DEFAULT']['fixedPostVars']['_DEFAULT'][] = array(
'GETvar' => 'arc[f-catalog-id]',
);

instead of

$TYPO3_CONF_VARS['EXTCONF']['realurl']['_DEFAULT']['postVarSets']['_DEFAULT']['arcavias'][] = array(
'GETvar' => 'arc[f-catalog-id]',
);

Using a default parameter with the "valueDefault" option doesn't help.

Norbert Sendetzky wrote:

There are two reasons why pages are not cached:
- Setting 'defaultToHTMLsuffixOnPrev' to something else than the default value
- Using optional parameters in the URL

There's a workaround available if you are using optional parameters: It only fails if an empty string is used for the optional parameter. If you set "emptySegmentValue" in the RealURL configuration to e.g. a dash (-), it works fine. Maybe the problem is that some code can't distinguish between an empty string and no parameter and generates the wrong cHash.

Norbert

Are all of your controller/actions cached(please post your ext_localconf.php)?

One simple case of failure is a "non-cached" extbase action. If you link to it inside extbase a cHash will be appended. However a cHash for a non-cached action is "nonsense" and will confuse realurl.

In case of non-caching actions make sure you use the noCacheHash=1 param in viewHelpers when linking to them.

Peter Niederlag wrote:

Are all of your controller/actions cached(please post your ext_localconf.php)?

No, not all my actions are cached but I had the same problem if only one cached plugin/action was placed on a single page. In this case it should work according to your explanation.

Norbert