Hello all,

I wonder if someone can help me with this encoding problem:

First, please click this link:
http://www.musicline.de/de/artist/Pege%A5Wilfer%A5Pauer%A5Pe
ge

In a browser, it brings a page and everything is fine.

However, when I try to download it with curl

curl -o local.HTM
http://www.musicline.de/de/artist/Pege%A5Wilfer%A5Pauer%A5Pe
ge

then I get a page where the artist line is changed from

Pege/Wilfer/Pauer/Pege to
PegeA5PauerA5Pege

Meaning: the second name (Wilfer) disappears and the
forward-slashes are displayed as "A5"'s.
So the resulting downloaded page is useless.

If I leave the string unencoded:

curl -o local.HTM
http://www.musicline.de/de/artist/Pege%A5Wilfer%A5Pauer%A5Pe
ge

then I get a page where the artist line is cut after the
first name, changing
Pege/Wilfer/Pauer/Pege to
Pege

and again, the page is useless.

I have been experimenting with quotes/no quotes, %A5
encoding for the slashes and %2F encoding, and everything
else under the sun. I have read the curl internal manual
from top to bottom and the pages about http scripting also.
No use - I cannot figure it out.

I understand the problem is the fact the search string
("Pege/Wilfer/Pauer/Pege") confuses the server because it
contains forward-slashes and the URL path contains them too,
but if the browser gets a correct page in return, curl must
SOMEHOW get one also.

The question is: How do I encode the slashes to make the
server understand the request?

Please help.....

-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing
real-time communications platform! Don't just IM. Build it in!
http://www.jabber.com/osdn/xim
Received on 2002-08-28