> > >tryit_edit.asp?filename=tryhtml_basic&referer=http://www.w3schools.com/html/html >_examples.asp > > >>and just this one is truncated. I think some regexp or pattern or >>explicit list of where_not_to_break_a_string characters would solve >>the problem. Or maybe it is already possible, but I dont know how? >> >> > >I think that some URL encoding has not happened somewhere. Whether wget or the >web server is at fault, I don't know, but the solution would be to URL encode >the slashes. > > 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. 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 !!! Only solution if you would try to make more people happy is to add some translation style and an option for selection. This is the same problem as with javascript urls. But here an "solution" could be theoretical defined for the url naming: - setup an webserver - wildcard domain *.mirror - error_hanlder page in the document_root - table that contain original_url to filename mapping filled by wget - the error handler cann strip of the .mirror and then return the propper content POSITIV: work for all URL styles NEGATIV: new Cocept, more work, not the original intention meet.
msg04276/pgp00000.pgp
Description: PGP signature
