Title: AAAHHH!!!!Name: Ted CambronDate: 2/8/2008 10:00:49 AMComment: Oh my gosh! A triple post! I refreshed twice and did not see the post and now this. Can someone fix this please?

Title: IssuesName: Ted CambronDate: 2/8/2008 9:58:26 AMComment: I just noticed, after some testing, that this "RFC compliant" abs_path regex allows for double dots (..) and that's unacceptable for my purposes and I'm sure many will agree with that without getting into details. I need to guarantee a secure path. This regex also allows for double forward slashes (//). That will throw an error in my case. I will look into this some more and make some updates that will go beyond RFC2396.

Title: IssuesName: Ted CambronDate: 2/8/2008 9:58:10 AMComment: I just noticed, after some testing, that this "RFC compliant" abs_path regex allows for double dots (..) and that's unacceptable for my purposes and I'm sure many will agree with that without getting into details. I need to guarantee a secure path. This regex also allows for double forward slashes (//). That will throw an error in my case. I will look into this some more and make some updates that will go beyond RFC2396.

Title: IssuesName: Ted CambronDate: 2/8/2008 9:58:04 AMComment: I just noticed, after some testing, that this "RFC compliant" abs_path regex allows for double dots (..) and that's unacceptable for my purposes and I'm sure many will agree with that without getting into details. I need to guarantee a secure path. This regex also allows for double forward slashes (//). That will throw an error in my case. I will look into this some more and make some updates that will go beyond RFC2396.