ConversationPropagationFilter active for non-JSF to-view-id

Similar to WELD-1044, if the <to-view-id> of an action results in a non-JSF URL:

<navigation-case>
<from-outcome>print</from-outcome>
<to-view-id>mypdf.pdf</to-view-id>
<redirect />
</navigation-case>

Then ConversationPropagationFilter not only appends 'cid' (which is fine, even though it will be ignored because '.pdf' is not a JSF URL) it also alters the extension from .pdf to .jsf.

This seems extreme? I understand ConversationPropagationFilter has a dilemma because the 'cid' it appends will be ignored. But I think the correct way to resolve this dilemma is not to append 'cid', rather than redirect the request.

This behaviour appears to be coming from the call to 'super.getActionURL' in 'ConversationAwareViewHandler'.