You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Grzegorz Tańczyk <go...@polzone.pl> on 2005/05/16 00:36:56 UTC

Wildcard and Regexp Matcher encoding problem

Hello,

  Can You tell me if it is a known issue that matchers malform
  encoding of nonUS characters? I have no problems when I run Cocoon
  2.1.5.1 on Windows, but when I try on Linux with Cocoon 2.1.6 then
  things go wrong.

  If there are two matches:

      <map:match type="regexp" pattern="page/(.*)">
        <map:redirect-to uri="cocoon:/page.html?page={1}"/>
      </map:match>  

      <map:match type="regexp" pattern="page.html">
        <map:generate....(sth. that use {request-param:page}
      </map:match>

  Then there is a diffrence when I request:
  page/i%C4%85%C4%99
  and
  page.html?page=i%C4%85%C4%99

  I dont know why but {1} != i%C4%85%C4%99 in first match, but
  everything is fine when I call second match directly.

  My question is: what was my mistake here?

  Thanks for any help
      
-- 
Best regards,
 Grzegorz                          mailto:goliatus@polzone.pl


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Wildcard and Regexp Matcher encoding problem

Posted by dynnamitt <kj...@gmail.com>.
Hi,

I got the same problem in 2.1.11... what's the solution?

regards
dynnamitt.


Grzegorz Tańczyk wrote:
> 
> Hello,
> 
>   Can You tell me if it is a known issue that matchers malform
>   encoding of nonUS characters? I have no problems when I run Cocoon
>   2.1.5.1 on Windows, but when I try on Linux with Cocoon 2.1.6 then
>   things go wrong.
> 
>   If there are two matches:
> 
>       <map:match type="regexp" pattern="page/(.*)">
>         <map:redirect-to uri="cocoon:/page.html?page={1}"/>
>       </map:match>  
> 
>       <map:match type="regexp" pattern="page.html">
>         <map:generate....(sth. that use {request-param:page}
>       </map:match>
> 
>   Then there is a diffrence when I request:
>   page/i%C4%85%C4%99
>   and
>   page.html?page=i%C4%85%C4%99
> 
>   I dont know why but {1} != i%C4%85%C4%99 in first match, but
>   everything is fine when I call second match directly.
> 
>   My question is: what was my mistake here?
> 
>   Thanks for any help
>       
> -- 
> Best regards,
>  Grzegorz                          mailto:goliatus@polzone.pl
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Wildcard-and-Regexp-Matcher-encoding-problem-tp39983p15450990.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

Re: Wildcard and Regexp Matcher encoding problem

Posted by dynnamitt <kj...@gmail.com>.
solution is described here:

http://www.nabble.com/Cocoon%2C-UTF-8-and-encodeURI-to7587213.html#a7595919

K-D

 

Grzegorz Tańczyk wrote:
> 
> Hello,
> 
>   Can You tell me if it is a known issue that matchers malform
>   encoding of nonUS characters? I have no problems when I run Cocoon
>   2.1.5.1 on Windows, but when I try on Linux with Cocoon 2.1.6 then
>   things go wrong.
> 
>   If there are two matches:
> 
>       <map:match type="regexp" pattern="page/(.*)">
>         <map:redirect-to uri="cocoon:/page.html?page={1}"/>
>       </map:match>  
> 
>       <map:match type="regexp" pattern="page.html">
>         <map:generate....(sth. that use {request-param:page}
>       </map:match>
> 
>   Then there is a diffrence when I request:
>   page/i%C4%85%C4%99
>   and
>   page.html?page=i%C4%85%C4%99
> 
>   I dont know why but {1} != i%C4%85%C4%99 in first match, but
>   everything is fine when I call second match directly.
> 
>   My question is: what was my mistake here?
> 
>   Thanks for any help
>       
> -- 
> Best regards,
>  Grzegorz                          mailto:goliatus@polzone.pl
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Wildcard-and-Regexp-Matcher-encoding-problem-tp39983p15451168.html
Sent from the Cocoon - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org