Reza,
<rule processing-point=3>
<request.property name="C-Man"
matches="http://www.w3.org/1999/06/24-CCPPexchange"; >
<action>transformContent</action>
</property>
</rule>
Notice the "request" prefix before the property tag which implies I am
referring to a header element in the request header which will not be
available in the response header.
Is there a way to do that with current IRML spec?
Yes, even at processing points 2 and 3, you can match request properties
in your rules. The provided property names may either be a request or a
response header. However, if the exact same header was present in both
the request and the response, you currently would have no means of
differentiating between these two in your rules. So maybe we should add
a differentiator to the property element as you suggested in your
example above. Comments?
-Andre