Hi Frank.

Your advise worked 100% thank you for the speedy reply.

Kind Regards
Derick.



Derick de Waal
Team Leader: Proteus Integration



M 0823249919 | T 011-8788121 | F
ddew...@imperial.co.za |


To read our email legal notice, browse to disclaimer.

-----Original Message-----
From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of 
Frank Gevaerts
Sent: 17 October 2016 05:26 PM
To: libcurl development <curl-library@cool.haxx.se>
Subject: Re: Headers in Rest Response

On Mon, Oct 17, 2016 at 03:11:32PM +0000, Derick de Waal wrote:
> Hi All.
>
> We have 2 servers test and production.
> On the production server we run curl 7.15.5 (x86_64-redhat-linux-gnu) 
> libcurl/7.15.5.
>
> On the test server we run curl 7.19.7 (x86_64-redhat-linux-gnu)
> libcurl/7.19.7
>
> On the production server when I make my GET call the output is fine and only 
> contains the XML.
> When I make the same call on the test server the output contains the HTTP 
> header information and I can't get it suppressed.
>
> Any idea how I can get around this?
>
>
> Command:
>
> curl -v   -k -insecure
>              -H "Accept:application/xml"
>              -o response.xml
>              https://client.com:9443/b2bservice/api/VendorOrder

-insecure? That means -i -n -s -e cure...
-i is "Include the HTTP-header in the output", which might be what you're 
seeing...

You might mean --insecure, but then you already have -k

(by the way, this might be more appropriate on the curl-users list)

Frank


--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are, by 
definition, not smart enough to debug it." - Brian W. Kernighan
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:  https://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:  https://curl.haxx.se/mail/etiquette.html

Reply via email to