By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,563 Members | 1,023 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,563 IT Pros & Developers. It's quick & easy.

sending http requests with curl but closing before reading the response

P: n/a
Is it possible to send http requests with curl but not have curl wait
for the response?

The reason I ask is because I'd like to code a web app that can sorta
start time consuming processes without the user having to wait. I'm
doing this (with fsockopen) by sending an http request to a page that
does the time consuming stuff and then immediatly closing, without
having read any of the response. This way, I don't have to wait for
the response.

Is it possible to do the same thing with curl? Sending just HEAD
requests doesn't work since it'd seem that the response (which I don't
yet know how to disable, if possible) is only sent at the end of the
pages execution. This might be a mod_gzip issue, but I'd rather use
fsockopen then disable mod_gzip.

Any ideas?

Jul 27 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
yawnmoth wrote:
Is it possible to send http requests with curl but not have curl wait
for the response?

The reason I ask is because I'd like to code a web app that can sorta
start time consuming processes without the user having to wait. I'm
doing this (with fsockopen) by sending an http request to a page that
does the time consuming stuff and then immediatly closing, without
having read any of the response. This way, I don't have to wait for
the response.

Is it possible to do the same thing with curl? Sending just HEAD
requests doesn't work since it'd seem that the response (which I don't
yet know how to disable, if possible) is only sent at the end of the
pages execution. This might be a mod_gzip issue, but I'd rather use
fsockopen then disable mod_gzip.

Any ideas?
Hi yawnmoth,

I think the best approach is to leave CURL and normal tcp/ip interaction
intact. This means: wait for the response.
In that way you actually know that system that performs the calculations is
up and running.

You can however make the heavycalc-script return its response immediately,
and THEN do the calculations.

Maybe someone has a more ellegant solution out there, but this could work:
1) use ob_start() at top of script
2) send a header telling the browser/CURL to go away:
header("Location: bla.html");
where bla.html is a small useless file. Maybe containing only 'doing calc'
or something.
3) flush it to the browser/CURL: ob_flush();

I expect as far as CULR is concerned, the respons ended, but you first
script can now continue doing your calculations.

Do not produce any output from here. Not sure where it goes if you do. :-)

Not tested. I think I solved that problem once like this. But it is quickly
tested by you. Please let us know if it works.

just my 2 cent

Regards,
Erwin Moller
Jul 27 '06 #2

P: n/a

Erwin Moller wrote:
yawnmoth wrote:

<snip>

Hi yawnmoth,

I think the best approach is to leave CURL and normal tcp/ip interaction
intact. This means: wait for the response.
In that way you actually know that system that performs the calculations is
up and running.

You can however make the heavycalc-script return its response immediately,
and THEN do the calculations.

Maybe someone has a more ellegant solution out there, but this could work:
1) use ob_start() at top of script
2) send a header telling the browser/CURL to go away:
header("Location: bla.html");
where bla.html is a small useless file. Maybe containing only 'doing calc'
or something.
3) flush it to the browser/CURL: ob_flush();

I expect as far as CULR is concerned, the respons ended, but you first
script can now continue doing your calculations.

Do not produce any output from here. Not sure where it goes if you do. :-)

Not tested. I think I solved that problem once like this. But it is quickly
tested by you. Please let us know if it works.

just my 2 cent
That's what register_shutdown_function used to do in PHP 4.0.6 and
earlier under Apache. Unforutnately, last time I tried it, it didn't
work with mod_gzip (I had to disable it for that to work).

Jul 27 '06 #3

P: n/a
yawnmoth wrote:
>
Erwin Moller wrote:
>yawnmoth wrote:

<snip>

Hi yawnmoth,

I think the best approach is to leave CURL and normal tcp/ip interaction
intact. This means: wait for the response.
In that way you actually know that system that performs the calculations
is up and running.

You can however make the heavycalc-script return its response
immediately, and THEN do the calculations.

Maybe someone has a more ellegant solution out there, but this could
work: 1) use ob_start() at top of script
2) send a header telling the browser/CURL to go away:
header("Location: bla.html");
where bla.html is a small useless file. Maybe containing only 'doing
calc' or something.
3) flush it to the browser/CURL: ob_flush();

I expect as far as CULR is concerned, the respons ended, but you first
script can now continue doing your calculations.

Do not produce any output from here. Not sure where it goes if you do.
:-)

Not tested. I think I solved that problem once like this. But it is
quickly tested by you. Please let us know if it works.

just my 2 cent
That's what register_shutdown_function used to do in PHP 4.0.6 and
earlier under Apache. Unforutnately, last time I tried it, it didn't
work with mod_gzip (I had to disable it for that to work).
well, did you try it?
Jul 27 '06 #4

P: n/a
On 27 Jul 2006 00:14:10 -0700, "yawnmoth" <te*******@yahoo.comwrote:
>Is it possible to send http requests with curl but not have curl wait
for the response?

The reason I ask is because I'd like to code a web app that can sorta
start time consuming processes without the user having to wait. I'm
doing this (with fsockopen) by sending an http request to a page that
does the time consuming stuff and then immediatly closing, without
having read any of the response. This way, I don't have to wait for
the response.

Is it possible to do the same thing with curl? Sending just HEAD
requests doesn't work since it'd seem that the response (which I don't
yet know how to disable, if possible) is only sent at the end of the
pages execution. This might be a mod_gzip issue, but I'd rather use
fsockopen then disable mod_gzip.
I suppose you could use CURLOPT_TIMEOUT set to a short timeout?

I'm not sure what the scope of CURLOPT_TIMEOUT is - if it's for the transfer
only, and CURLOPT_CONNECTION_TIMEOUT is specifically for the handshaking, then
it ought to fit your purpose.

--
Andy Hassall :: an**@andyh.co.uk :: http://www.andyh.co.uk
http://www.andyhsoftware.co.uk/space :: disk and FTP usage analysis tool
Jul 27 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.