Re: cURL and response code 302

From	Scott Johnson <noonehome@chalupasworld.com>
Newsgroups	comp.lang.php
Subject	Re: cURL and response code 302
Date	2013-07-10 16:13 -0700
Organization	A noiseless patient Spider
Message-ID	<krkpgf$j1j$1@dont-email.me> (permalink)
References	(2 earlier) <krh5it$s6a$1@speranza.aioe.org> <51DC1D1D.3090905@arnowelzel.de> <krh82d$4hl$1@speranza.aioe.org> <lE5Dt.41228$T55.1895@fx16.iad> <krjrsl$s38$2@speranza.aioe.org>

Show all headers | View raw

On 7/10/2013 7:42 AM, bill wrote:
> On 7/10/2013 12:44 AM, Daniel Pitts wrote:
>> On 7/9/13 7:51 AM, bill wrote:
>>> 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.
>>>
>>> bill
>>
>> Actually, suggesting that you RTFM yourself would have been most
>> clear. I understand not knowing about Location and HTTP spec, and
>> not knowing where to look for that.  You should learn how to find
>> things in libraries that you're using though.
>
> Actually, I not only read the manual, I studied it (and the coments) and
> still missed curlopt_header.... (as usual) until I had sent my first
> message.
>
> Sometimes when you are new to an area it is hard to find/understand the
> fine print.
>
> bill
>
>
I like to think of the premise that if you don't know what you don't 
know, you don't know what there is to know.

Scotty

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