Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #10053
| From | Arno Welzel <usenet@arnowelzel.de> |
|---|---|
| Newsgroups | comp.lang.php |
| Subject | Re: cURL and response code 302 |
| Date | 2013-07-09 17:20 +0200 |
| Message-ID | <51DC2A36.7090005@arnowelzel.de> (permalink) |
| References | <krem8f$epd$1@speranza.aioe.org> <uoBCt.963$t_.539@newsfe11.iad> <krh5it$s6a$1@speranza.aioe.org> <51DC1D1D.3090905@arnowelzel.de> <krh82d$4hl$1@speranza.aioe.org> |
Am 09.07.2013 16:51, schrieb bill: > On 7/9/2013 10:24 AM, Arno Welzel wrote: >> Am 09.07.2013 16:09, schrieb bill: >> >>> On 7/8/2013 12:02 PM, Daniel Pitts wrote: >>>> On 7/8/13 8:35 AM, bill wrote: >>>>> when I have cUrl seet up with CURLOPT_FOLLOWLOCATION =>FALSE, >>>>> I am getting a 302, moved temporarily. >>>>> >>>>> How do I find out the URL it is being redirected to ? >>>>> The effectiveURL that is returned is the one I sent the request >>>>> to. >>>>> >>>>> bill >>>> >>>> The "Location" response header contains the desired URL. >>>> >>>> See: >>>> <http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3> >>> >>> Thanks, is there a way to obtain the Location response header >>> from cURL ? >> >> Maybe this example in the documentation may help: >> >> <http://www.php.net/manual/en/function.curl-exec.php#80442> >> >> >> > actually, suggesting that I look at curlopt_header would have > been more clear. Maybe - but since it is also neccessary to check the header size to separate the header from the body I refered to the example. And finally you got the right hint - didn't you? ;-) -- Arno Welzel http://arnowelzel.de http://de-rec-fahrrad.de
Back to comp.lang.php | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
cURL and response code 302 bill <william@TechServSys.com> - 2013-07-08 11:35 -0400
Re: cURL and response code 302 Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-07-08 09:02 -0700
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-09 10:09 -0400
Re: cURL and response code 302 Arno Welzel <usenet@arnowelzel.de> - 2013-07-09 16:24 +0200
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-09 10:51 -0400
Re: cURL and response code 302 Arno Welzel <usenet@arnowelzel.de> - 2013-07-09 17:20 +0200
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-10 10:40 -0400
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-10 11:09 -0400
Re: cURL and response code 302 Arno Welzel <usenet@arnowelzel.de> - 2013-07-11 00:12 +0200
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-11 10:51 -0400
Re: cURL and response code 302 Arno Welzel <usenet@arnowelzel.de> - 2013-07-11 21:04 +0200
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-12 09:58 -0400
Re: cURL and response code 302 Daniel Pitts <newsgroup.nospam@virtualinfinity.net> - 2013-07-09 21:44 -0700
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-10 10:42 -0400
Re: cURL and response code 302 Scott Johnson <noonehome@chalupasworld.com> - 2013-07-10 16:13 -0700
Re: cURL and response code 302 bill <william@TechServSys.com> - 2013-07-12 09:59 -0400
Re: cURL and response code 302 kyrpog83@gmail.com - 2014-04-10 10:23 -0700
csiph-web