"I'm partial to /\w.*@.*\w.*\..*\w/ -- ensure theres one alnum_ before the @, one alnum_ after, and a dot followed by another alnum_ - should take care of ip addresses, missing suffixes, etc, at a high level. The only 'real' validation is attempting to send the mail and getting some sort of validation back (tracking pixel, clickback, whatever)"
- Justin Hart
"I'm partial to /\w.*@.*\w.*\..*\w/ -- ensure theres one alnum_ before the @, one alnum_ after, and a dot followed by another alnum_ - should take care of ip addresses, missing suffixes, etc, at a high level. The only 'real' validation is attempting to send the mail and getting some sort of validation back (tracking pixel, clickback, whatever)"
- Justin Hart
"IMO you ~should~ always look at the request method as given in the HTTP headers by your container (apache, fpm, the magical 5.4 server, etc) if you're trying to put behavior on that. $_GET and $_POST are technically able to live together in the same request - if a POST has a multipart or urlencoded body, those body params end up in $_POST, but querystring parameters end up in $_GET. Separate the handling of the HTTP method from the source of parameters. $_GET just happens to be the parameters encoded in the querystring, $_POST happens to be the body parameters in either urlencoded or multipart encoded, and php://input or $HTTP_RAW_POST_DATA (which is kinda useless since you have to turn it on in INI) are the request body plain. the PECL extension does seem to 'help' in encapsulating the parameters, but you're right, it should do more with an integration with the input filter, etc."
- Justin Hart
RT @NathanFillion: Yes, you can download #TuckerAndDaleVsEvil, but it's in theaters now!! "Yer friend mus' be allergic t'bees..." http:/ ...
- Justin Hart