NYCPHP Meetup

[Matt Kaufman]

Oh, PS and 201 means that you probably achieved what you were trying
to do ;)  So no wonder you are tired....

10.2.2 201 Created

   The request has been fulfilled and resulted in a new resource being
   created. The newly created resource can be referenced by the URI(s)
   returned in the entity of the response, with the most specific URI
   for the resource given by a Location header field. The response
   SHOULD include an entity containing a list of resource
   characteristics and location(s) from which the user or user agent can
   choose the one most appropriate. The entity format is specified by
   the media type given in the Content-Type header field. The origin
   server MUST create the resource before returning the 201 status code.
   If the action cannot be carried out immediately, the server SHOULD
   respond with 202 (Accepted) response instead.

   A 201 response MAY contain an ETag response header field indicating
   the current value of the entity tag for the requested variant just
   created, see section 14.19.

On Sat, Jul 9, 2011 at 11:36 PM, Matt Kaufman <mkfmncom at gmail.com> wrote:
> == Memorize Now ==
>      - 1xx: Informational - Request received, continuing process
>
>      - 2xx: Success - The action was successfully received,
>        understood, and accepted
>
>      - 3xx: Redirection - Further action must be taken in order to
>        complete the request
>
>      - 4xx: Client Error - The request contains bad syntax or cannot
>        be fulfilled
>
>      - 5xx: Server Error - The server failed to fulfill an apparently
>
> == And Know Soon!! :) ==
>     Status-Code    =
>            "100"  ; Section 10.1.1: Continue
>          | "101"  ; Section 10.1.2: Switching Protocols
>          | "200"  ; Section 10.2.1: OK
>          | "201"  ; Section 10.2.2: Created
>          | "202"  ; Section 10.2.3: Accepted
>          | "203"  ; Section 10.2.4: Non-Authoritative Information
>          | "204"  ; Section 10.2.5: No Content
>          | "205"  ; Section 10.2.6: Reset Content
>          | "206"  ; Section 10.2.7: Partial Content
>          | "300"  ; Section 10.3.1: Multiple Choices
>          | "301"  ; Section 10.3.2: Moved Permanently
>          | "302"  ; Section 10.3.3: Found
>          | "303"  ; Section 10.3.4: See Other
>          | "304"  ; Section 10.3.5: Not Modified
>          | "305"  ; Section 10.3.6: Use Proxy
>          | "307"  ; Section 10.3.8: Temporary Redirect
>          | "400"  ; Section 10.4.1: Bad Request
>          | "401"  ; Section 10.4.2: Unauthorized
>          | "402"  ; Section 10.4.3: Payment Required
>          | "403"  ; Section 10.4.4: Forbidden
>          | "404"  ; Section 10.4.5: Not Found
>          | "405"  ; Section 10.4.6: Method Not Allowed
>          | "406"  ; Section 10.4.7: Not Acceptable
>          | "407"  ; Section 10.4.8: Proxy Authentication Required
>          | "408"  ; Section 10.4.9: Request Time-out
>          | "409"  ; Section 10.4.10: Conflict
>          | "410"  ; Section 10.4.11: Gone
>          | "411"  ; Section 10.4.12: Length Required
>          | "412"  ; Section 10.4.13: Precondition Failed
>          | "413"  ; Section 10.4.14: Request Entity Too Large
>          | "414"  ; Section 10.4.15: Request-URI Too Large
>          | "415"  ; Section 10.4.16: Unsupported Media Type
>          | "416"  ; Section 10.4.17: Requested range not satisfiable
>          | "417"  ; Section 10.4.18: Expectation Failed
>          | "500"  ; Section 10.5.1: Internal Server Error
>          | "501"  ; Section 10.5.2: Not Implemented
>          | "502"  ; Section 10.5.3: Bad Gateway
>          | "503"  ; Section 10.5.4: Service Unavailable
>          | "504"  ; Section 10.5.5: Gateway Time-out
>          | "505"  ; Section 10.5.6: HTTP Version not supported
>
>
> On Sat, Jul 9, 2011 at 11:10 PM, Margaret Waldman <mmwaldman at nyc.rr.com> wrote:
>> Thank you.  I’m getting 201 now.  I’m tired.  It’s nap time.
>>
>> From: Kristina Anderson
>> Sent: Saturday, July 09, 2011 6:44 PM
>> To: talk at lists.nyphp.org
>> Subject: Re: [nycphp-talk] curl
>>
>> 400 sounds like a server response code not a cURL error code...
>>
>> HTTP response code 400 is a syntax error in your HTTP request.
>>
>> K
>>
>> On 7/9/2011 5:24 PM, Margaret Waldman wrote:
>>
>> Thank you in advanced.
>>
>> From: Margaret Waldman
>> Sent: Saturday, July 09, 2011 5:24 PM
>> To: NYPHP Talk
>> Subject: [nycphp-talk] curl
>>
>> What is a curl return error of 400?
>>
>> Margaret Michele Waldman
>> ________________________________
>> _______________________________________________
>> New York PHP Users Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>>
>> http://www.nyphp.org/Show-Participation
>>
>> _______________________________________________
>> New York PHP Users Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>>
>> http://www.nyphp.org/Show-Participation
>>
>> ________________________________
>> _______________________________________________
>> New York PHP Users Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>>
>> http://www.nyphp.org/Show-Participation
>>
>> _______________________________________________
>> New York PHP Users Group Community Talk Mailing List
>> http://lists.nyphp.org/mailman/listinfo/talk
>>
>> http://www.nyphp.org/Show-Participation
>>
>