Some tags for searching: unicode, no_script_tag, prod, decode,
decoding, path

This post is not supposed to be one about "how to use symfony" but
rather a question about a functional impact

The prod environment especially with no_script_tag set to on should
not differ in functionality from other enviroments, right?

I have enabled logging for prod and noticed some strange behaviour
with decoding already encoded data.

The call is the same, I call for something with encoded special chars,
for instance a '&'

The call
/something/A & B
is encoded correctly to:
/something/A%2B%2526%2BB
that is perfectly fine.

Calling now once the no script version and the script directly results
in these calls:
domain.tld/something/A%2B%2526%2BB
and
domain.tld/index.php/something/A%2B%2526%2BB

Both calls are redirected to the index.php which is correct. BUT the
passed data is encoded completly different:
No_Script Version: The parameter is called "A%2B%2526%2BB"
Script Version whereas has the variables "A & B"
This is supposed to be default behaviour, since dev does the same
thing. The no_script version fails to execute since the parameter is
wrong.
How does rewriting rules affect the encoding? Are there additional
headers missed to be sent?

The htaccess file is the default one found in every fresh sf project.

This behaviour is confirmed on windows and linux with an apache

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to