Either use Wireshark or look at the Curl documentation. On a quick glance, either --verbose or --trace make Curl dump everything it sends or receives.
Again, you will have to learn Curl and HTTP in either case, so now is a good time to start with that.
As I now found out, I already said the same, even more verbose, in Re: CURL and Perl (it rhymes!). So maybe re-reading that thread helps.
| [reply] [d/l] [select] |
Hi Corion,
So I tried the -v option and I got some more info, which follows, but I wouldn't know how to match this to the code you posted in the other thread.
It seems to do a POST and then there seem to be some fields with some values, is that correct? Like User-Agent: curl/7.35.0
What do you think?
Steve.
* Hostname was NOT found in DNS cache
* Trying xxx.xxx.xxx.xxx...
% Total % Received % Xferd Average Speed Time Time Time
+ Current
Dload Upload Total Spent Left
+ Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:
+-- 0* Connected to xxx.xxx.xxx.xxx(xxx.xxx.xxx.xxx) port 8098 (#0
+)
> POST /api/resultados/ HTTP/1.1
> User-Agent: curl/7.35.0
> Host: xxx.xxx.xxx.xxx:8098
> Accept: */*
> Authorization: Token xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Content-Length: 949
> Expect: 100-continue
> Content-Type: multipart/form-data; boundary=------------------------
+daf19fd44f6a97e8
>
* Done waiting for 100-continue
0 949 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:
+-- 0} [data not shown]
< HTTP/1.1 100 Continue
< HTTP/1.1 201 CREATED
* Server nginx/1.1.19 is not blacklisted
< Server: nginx/1.1.19
< Date: Sun, 01 Feb 2015 14:48:34 GMT
< Content-Type: application/xml; charset=utf-8
< Transfer-Encoding: chunked
<
< [data not shown]
Connection: keep-alive
< Vary: Accept
< X-Frame-Options: SAMEORIGIN
< Allow: GET, POST, HEAD, OPTIONS
<
{ [data not shown]
100 1142 0 193 100 949 84 416 0:00:02 0:00:02 --:--:
+-- 416
100 1142 0 193 100 949 84 416 0:00:02 0:00:02 --:--:
+-- 416
* Connection #0 to host xxx.xxx.xxx.xxx left intact
| [reply] [d/l] |
Now would be a good time to learn about HTTP, so you learn what the headers mean, and what the payload of the request means, and how you can replicate that with LWP::UserAgent (or any other HTTP client). I don't see much way around that.
| [reply] |
Did you read the thread you linked to in the OP?
| [reply] |
| [reply] |