Ack,
Pasting below updated commit message. I hope it is more clear now...
build: fix circular header inclusion with other packages
This commit renames lib/setup.h to lib/curl_setup.h and
renames lib/setup_once.h to lib/curl_setup_once.h.
Removes the need and usage of a header inclusion guard
On Tue, Jan 8, 2013 at 11:51 AM, GitHub nore...@github.com wrote:
Branch: refs/heads/master
Home: https://github.com/bagder/curl
Commit: 7a6d8b1b1a8fcc184c36d6b6e741e32250b4bacb
https://github.com/bagder/curl/commit/7a6d8b1b1a8fcc184c36d6b6e741e32250b4bacb
Author: Daniel
On Tue, Jan 8, 2013, Daniel Stenberg wrote:
I accidentally posted a version that wasn't the latest rebase yesterday, and
with Steve Holme's POP3 TLS fix this morning (that required a little extra
merge edit) I decided to post a follow-up version. Nothing else changed.
Hi Daniel,
I'm trying
On Tue, Jan 08, 2013 at 11:12:14PM +0700, Dung Nguyen wrote:
hi!
I have server with i need to call the request like this
GET /test
HTTP/1.1
I'm assuming that this is the URL-decoded version of
GET /test%0a%0a and not some other unprintable characters. Not that it
really matters, because
On Tue, 8 Jan 2013, Yang Tse wrote:
this change we are leaving behind in the dust those using autoconf 2.57 for
probably no good reason, including IRIX autobuilds.
...
Changing AC_LIBTOOL_WIN32_DLL and AC_PROG_LIBTOOL with LT_INIT rises libtool
version requirement from 1.4.2 all the way up
On Tue, 8 Jan 2013, Dung Nguyen wrote:
I have server with i need to call the request like this
*GET /test*
*
*
* HTTP/1.1*
You can often make libcurl misbehave in many ways, but I don't think you can
force libcurl to do such a protocol violation unless you change lib/url.c and
recompile.
On Tue, 8 Jan 2013, Michael Wood wrote:
I imagine getting curl to accept Welcome to the server\nHTTP/1.1 200 OK...
as a response would also require modifications?
Oh right. I didn't even spot that part. That part would possibly require a
more complicated modification...
--
/
On Tue, Jan 8, 2013, Daniel Stenberg wrote:
Those line endings are a bit painful to handle in patches. Try the attached
gzip version and see if it makes anything better!
Perfect!
Building now...
--
-=[Yang]=-
---
List admin:
On Tue, 8 Jan 2013, Yang Tse wrote:
Pasting below updated commit message. I hope it is more clear now...
Awesome, thanks for that excellent clarification. Now I'm all good and happy.
Carry on! =)
--
/ daniel.haxx.se
---
List
Daniel,
Patch applies cleanly on top of fea3a3d5.
Builds successfully with:
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s
rtsp scp sftp smtp smtps telnet tftp
Features: Debug TrackMemory IDN Largefile NTLM NTLM_WB SSL libz TLS-SRP
Nearly all test cases pass except for:
ok, i see...
if i want it work then i need to modify a lots of thing. The thing is
server is not mine, and i need to follow them, too bad :D
2013/1/9 Daniel Stenberg dan...@haxx.se
On Tue, 8 Jan 2013, Michael Wood wrote:
I imagine getting curl to accept Welcome to the server\nHTTP/1.1 200
Title: Re: CURL custom request
Hello Dung,
You may try curl_easy_send()/curl_easy_recv() functions to send your custom request and receive the nonstandard response.
These functions are protocol-agnostic, so you will have to parse the response in your code.
Wednesday, January 9, 2013, 8:25:42
12 matches
Mail list logo
