On Sat, Jun 14, 2008 at 4:30 PM, Tony Lewis <[EMAIL PROTECTED]> wrote: > mm w wrote: > >> Hi, after all, after all it's only my point of view :D >> anyway, >> >> "/dir/file", >> "dir/File", non-standard >> "Dir/file", non-standard >> and "/Dir/File" non-standard > > According to RFC 2396: The path component contains data, specific to the > authority (or the scheme if there is no authority component), identifying the > resource within the scope of that scheme and authority. > > In other words, those names are well within the standard when the server > understands them. As far as I know, there is nothing in Internet standards > restricting mixed case paths. > :) read again, nobody does except some punk-head folks
>> that's it, if the server manages non-standard URL, it's not my >> concern, for me it doesn't exist > > Oh. I see. You're writing to say that wget should only implement features > that are meaningful to you. Thanks for your narcissistic input. no i'm not such a jerk, a simple grep/sed on the website source to remove the malicious URL should be fine, or an HTTP redirection when the malicious non-standard URL is called in other hand, if wget changes every links in lowercase, some people should have the opposite problem a golden rule: never distributing mixed-case URL (to your users), a simple respect for them and everything in lower-case > > Tony > > -- -mmw
