Thanks Steve. I don't understand the syntax: in the regex versions I use, . means
one and just one character, not any string.
Any string excluding the null-string would be .+ or ..*
More generally, I still have problems with validation as a concept: it's too
difficult, and perhaps that's why
: [mapserver-users] RE: Validation beyond [A-z]
Thanks Steve. I don't understand the syntax: in the regex versions I use, .
means one and just one character, not any string.
Any string excluding the null-string would be .+ or ..*
More generally, I still have problems with validation as a concept: it's too
-users] RE: Validation beyond [A-z]
Thanks Steve. I don't understand the syntax: in the regex versions I use, .
means one and just one character, not any string.
Any string excluding the null-string would be .+ or ..*
More generally, I still have problems with validation as a concept: it's too
On 4/29/2011 6:37 AM, Jan Hartmann wrote:
Thanks Steve. I don't understand the syntax: in the regex versions I
use,. meansone and just one character, not any string. Any
string excluding the null-string would be.+ or..*
Not . means match any single character in the string. It does not mean
I find the whole validation issue difficult and not well documented
(http://trac.osgeo.org/mapserver/ticket/3754, last updated four hours
ago). How do I put all validation off? I really don need that much security.
Jan
On 04/28/11 18:19, Lime, Steve D (DNR) wrote:
I see the problem, just
Hi Jan,
I do not think there is a global OFF switch for validation, but where
validation is required you can include the regex validation string of
/./ which means match anything except a null string, or to also accept a
null string then use /.*/
You still need to be aware of when you
I could not find a ticket for this probelm so I have aopened a new one:
http://trac.osgeo.org/mapserver/ticket/3853
Please add yourselves to the CC list if you want to follow along on
updates. Also if you are aware of other areas of the code or mapfile
that need to add support for UTF-8