Thomas Lussnig wrote: > Why should be there an url encoding ? > / are an legal character in url and in the GET string. > Ist used for example for Path2Query translation. > > The main problem is that wget need to translate an URL to and > Filesystem name.
Yes, you are right, I wasn't think clearly. > Filesystem names are PATH and FILE names. And wget do it right i > think. > > example: > > http://my.domain/dyn_page.sql/content_id/1891/session/0815 > > Server: > > File: /dyn_page.sql > Query String /content_id/1891/session/0815 > > Client: > 0. dyn_page.sql/content_id/1891/session/0815 (current i think) > 1. dyn_page.sql_content_id_1891_session_0815 > 2. 0815 > > Only the Author of the webpage could tell you what is an good > translation from an URL to filesystem > if there is an querystring on the page, else ALL solutions have their > bad sites !!! ?? The problem is that with a ?x=y, where y contains slashes, wget passes them unchanged to the OS, causing directories to be created, but fails to adjyst relative links to account for the fact that the page is in a deeper directory that it should be. The solution is to map / to _ or something. Max.
