%PDF- %PDF-
Direktori : /home/graphicd/www/vebto/vendor/rackspace/php-opencloud/doc/_build/doctrees/ |
Current File : /home/graphicd/www/vebto/vendor/rackspace/php-opencloud/doc/_build/doctrees/debugging.doctree |
�cdocutils.nodes document q)�q}q(U nametypesq}q(X debuggingqNX add to your clientqNX an example with swiftqNX strategy 2: wire loggingq NX install the pluginq NX) strategy 1: meaningful exception handlingqNuUsubstitution_defsq}q Uparse_messagesq]qUcurrent_sourceqNU decorationqNUautofootnote_startqKUnameidsq}q(hU debuggingqhUadd-to-your-clientqhUan-example-with-swiftqh Ustrategy-2-wire-loggingqh Uinstall-the-pluginqhU(strategy-1-meaningful-exception-handlingquUchildrenq]qcdocutils.nodes section q)�q}q(U rawsourceq U Uparentq!hUsourceq"X2 /Users/jamie/projects/php/v1-sdk/doc/debugging.rstq#Utagnameq$Usectionq%U attributesq&}q'(Udupnamesq(]Uclassesq)]Ubackrefsq*]Uidsq+]q,haUnamesq-]q.hauUlineq/KUdocumentq0hh]q1(cdocutils.nodes title q2)�q3}q4(h X Debuggingq5h!hh"h#h$Utitleq6h&}q7(h(]h)]h*]h+]h-]uh/Kh0hh]q8cdocutils.nodes Text q9X Debuggingq:��q;}q<(h h5h!h3ubaubcdocutils.nodes paragraph q=)�q>}q?(h Xf There are two important debugging strategies to use when encountering problems with HTTP transactions.q@h!hh"h#h$U paragraphqAh&}qB(h(]h)]h*]h+]h-]uh/Kh0hh]qCh9Xf There are two important debugging strategies to use when encountering problems with HTTP transactions.qD��qE}qF(h h@h!h>ubaubh)�qG}qH(h U h!hh"h#h$h%h&}qI(h(]h)]h*]h+]qJhah-]qKhauh/Kh0hh]qL(h2)�qM}qN(h X) Strategy 1: Meaningful exception handlingqOh!hGh"h#h$h6h&}qP(h(]h)]h*]h+]h-]uh/Kh0hh]qQh9X) Strategy 1: Meaningful exception handlingqR��qS}qT(h hOh!hMubaubh=)�qU}qV(h X� If the API returns a ``4xx`` or ``5xx`` status code, it indicates that there was an error with the sent request, meaning that the transaction cannot be adequately completed.h!hGh"h#h$hAh&}qW(h(]h)]h*]h+]h-]uh/K h0hh]qX(h9X If the API returns a qY��qZ}q[(h X If the API returns a h!hUubcdocutils.nodes literal q\)�q]}q^(h X ``4xx``h&}q_(h(]h)]h*]h+]h-]uh!hUh]q`h9X 4xxqa��qb}qc(h U h!h]ubah$Uliteralqdubh9X or qe��qf}qg(h X or h!hUubh\)�qh}qi(h X ``5xx``h&}qj(h(]h)]h*]h+]h-]uh!hUh]qkh9X 5xxql��qm}qn(h U h!hhubah$hdubh9X� status code, it indicates that there was an error with the sent request, meaning that the transaction cannot be adequately completed.qo��qp}qq(h X� status code, it indicates that there was an error with the sent request, meaning that the transaction cannot be adequately completed.h!hUubeubh=)�qr}qs(h X� The Guzzle HTTP component, which forms the basis of our SDK's transport layer, utilizes `numerous exception classes <https://github.com/guzzle/guzzle/tree/master/src/Guzzle/Http/Exception>`__ to handle this error logic.h!hGh"h#h$hAh&}qt(h(]h)]h*]h+]h-]uh/Kh0hh]qu(h9XX The Guzzle HTTP component, which forms the basis of our SDK's transport layer, utilizes qv��qw}qx(h XX The Guzzle HTTP component, which forms the basis of our SDK's transport layer, utilizes h!hrubcdocutils.nodes reference qy)�qz}q{(h Xg `numerous exception classes <https://github.com/guzzle/guzzle/tree/master/src/Guzzle/Http/Exception>`__h&}q|(UnameX numerous exception classesUrefuriq}XF https://github.com/guzzle/guzzle/tree/master/src/Guzzle/Http/Exceptionh+]h*]h(]h)]h-]uh!hrh]q~h9X numerous exception classesq��q�}q�(h U h!hzubah$U referenceq�ubh9X to handle this error logic.q���q�}q�(h X to handle this error logic.h!hrubeubh=)�q�}q�(h X* The two most common exception classes are:q�h!hGh"h#h$hAh&}q�(h(]h)]h*]h+]h-]uh/Kh0hh]q�h9X* The two most common exception classes are:q���q�}q�(h h�h!h�ubaubcdocutils.nodes bullet_list q�)�q�}q�(h U h!hGh"h#h$Ubullet_listq�h&}q�(Ubulletq�X -h+]h*]h(]h)]h-]uh/Kh0hh]q�(cdocutils.nodes list_item q�)�q�}q�(h Xg ``Guzzle\Http\Exception\ClientErrorResponseException``, which is thrown when a ``4xx`` response occurs h!h�h"h#h$U list_itemq�h&}q�(h(]h)]h*]h+]h-]uh/Nh0hh]q�h=)�q�}q�(h Xf ``Guzzle\Http\Exception\ClientErrorResponseException``, which is thrown when a ``4xx`` response occursh!h�h"h#h$hAh&}q�(h(]h)]h*]h+]h-]uh/Kh]q�(h\)�q�}q�(h X6 ``Guzzle\Http\Exception\ClientErrorResponseException``h&}q�(h(]h)]h*]h+]h-]uh!h�h]q�h9X2 Guzzle\Http\Exception\ClientErrorResponseExceptionq���q�}q�(h U h!h�ubah$hdubh9X , which is thrown when a q���q�}q�(h X , which is thrown when a h!h�ubh\)�q�}q�(h X ``4xx``h&}q�(h(]h)]h*]h+]h-]uh!h�h]q�h9X 4xxq���q�}q�(h U h!h�ubah$hdubh9X response occursq���q�}q�(h X response occursh!h�ubeubaubh�)�q�}q�(h Xg ``Guzzle\Http\Exception\ServerErrorResponseException``, which is thrown when a ``5xx`` response occurs h!h�h"h#h$h�h&}q�(h(]h)]h*]h+]h-]uh/Nh0hh]q�h=)�q�}q�(h Xf ``Guzzle\Http\Exception\ServerErrorResponseException``, which is thrown when a ``5xx`` response occursh!h�h"h#h$hAh&}q�(h(]h)]h*]h+]h-]uh/Kh]q�(h\)�q�}q�(h X6 ``Guzzle\Http\Exception\ServerErrorResponseException``h&}q�(h(]h)]h*]h+]h-]uh!h�h]q�h9X2 Guzzle\Http\Exception\ServerErrorResponseExceptionq���q�}q�(h U h!h�ubah$hdubh9X , which is thrown when a q �q�}q�(h X , which is thrown when a h!h�ubh\)�q�}q�(h X ``5xx``h&}q�(h(]h)]h*]h+]h-]uh!h�h]q�h9X 5xxqɅ�q�}q�(h U h!h�ubah$hdubh9X response occursq̅�q�}q�(h X response occursh!h�ubeubaubeubh=)�q�}q�(h XE Both of these classes extend the base ``BadResponseException`` class.q�h!hGh"h#h$hAh&}q�(h(]h)]h*]h+]h-]uh/Kh0hh]q�(h9X&