ModSecurity

Telepac wrote:

> I'm Portuguese
> I have problem with GET or POST whenever I intend to send characters as=
 for
> eg: " =E1 " or " =E9 "

  You are likely restricting requests with:

  SecFilterForceByteRange FROM TO (set FROM to 0 and TO to 255)

  or

  SecFilterCheckUnicodeEncoding (should be off unless you know
  what you're doing)

  But you should really send us your full mod_security configuration
  so we can see for ourselves.

--=20
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

What is the DefaultCharset you are using?
Those are not portugeses characters, they are also spanish characters :(


Telepac wrote:

> I'm Portuguese
> I have problem with GET or POST whenever I intend to send characters as=
 for
> eg: " =E1 " or " =E9 "
>=20
> please help me
>=20
> Best regards
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKN=
D
> _______________________________________________
> mod-security-users mailing list
> mod-security-users@...
> https://lists.sourceforge.net/lists/listinfo/mod-security-users
>=20

Luis Miguel Cruz wrote:

> What is the DefaultCharset you are using?
> Those are not portugeses characters, they are also
> spanish characters :(

  There are no restrictions by default (if there are - that would be a
  bug), it all depends on your configuration. Also, HTTP does not
  care about character encodings.

-- 
ModSecurity (http://www.modsecurity.org)
[ Open source IDS for Web applications ]

Well, I only spoke from my experience.
I didn=B4t know if there was a relation with the charset configuration=20
from httpd.conf and mod_security

Ivan Ristic wrote:

> Luis Miguel Cruz wrote:
>=20
>=20
>>What is the DefaultCharset you are using?
>>Those are not portugeses characters, they are also
>>spanish characters :(
>=20
>=20
>   There are no restrictions by default (if there are - that would be a
>   bug), it all depends on your configuration. Also, HTTP does not
>   care about character encodings.
>=20