how do i force curl to NOT interpret {} and [] as multi-URL specifications?

(You): how do i force curl to NOT interpret {} and [] as multi-URL specifications?

(aside from using %xx coding, which is ugly)

———————-

(Chris): You can try using in front of them.

(You): Johnson, doesn’t work (I did try that first). Of course, I’m running from tcsh, so I might need to the itself?

(Chris): You might need \ in order to punch the through tcsh to curl. Another thing you can do is just write a very short /bin/sh script with what you want in it. That way you can edit, write, test.

(You): I actually wrote a sh one-liner… that works, but %xx looks ugly and, eyeball-wise, it’s hard to see %48 as { and %4a (or whatever) as }.

(Chris): Yes, but if you are using /bin/sh you can ‘http://xxx.example.com/my.php?xyx{abc}’ [http://xxx.example.com/my.php?xyx{abc}’] with the single quotes and that might work with curl. If it doesn’t, you can add the {abc} and don’t have to worry about the stripping of extra characters.

(Chris): and why don’t you just ask me directly?

———————-

(Kevin): Instead of %xx coding, try xxx coding.

;)

(You): what does that mean? :)

[Vark assigned category: curl, more details]

This entry was posted in Barry After Vark. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *