If the url is not conform to date-based archiving, this unexpectedly wouldn't lead to an error. 

I noticed this today, as some weird urls showed up in the google index for one of my projects. 

Since ArticlesRouter just passes the parameters through, the ArticlesContainer would always fall back to interpreting the request as an archive (even if a resource with this url doesn't exist and the parameters don't have anything in common with dates). As a result MODx will always return a HTTP 200 status, which is really bad.

To fix this, we have to validate the parameters for numeric values and return false if they are invalid.