@@ -214,7 +214,7 @@ cookie
214214======
215215
216216This specifies the filename that CURL should use to read cookie values from, and
217- to save cookie values to. This is done using the CURL_COOKIEJAR and CURL_COOKIEFILE options.
217+ to save cookie values to. This is done using the `` CURL_COOKIEJAR `` and `` CURL_COOKIEFILE `` options.
218218An example:
219219
220220.. literalinclude :: curlrequest/021.php
@@ -223,8 +223,10 @@ debug
223223=====
224224
225225When ``debug `` is passed and set to ``true ``, this will enable additional debugging to echo to STDERR during the
226- script execution. This is done by passing CURLOPT_VERBOSE and echoing the output. So, when you're running a built-in
227- server via ``spark serve `` you will see the output in the console. Otherwise, the output will be written to
226+ script execution.
227+
228+ This is done by passing ``CURLOPT_VERBOSE `` and echoing the output. So, when you're running a built-in
229+ server via ``spark serve ``, you will see the output in the console. Otherwise, the output will be written to
228230the server's error log.
229231
230232.. literalinclude :: curlrequest/034.php
@@ -270,8 +272,11 @@ further headers arrays or calls to ``setHeader()``.
270272http_errors
271273===========
272274
273- By default, CURLRequest will fail if the HTTP code returned is greater than or equal to 400. You can set
274- ``http_errors `` to ``false `` to return the content instead:
275+ By default, CURLRequest will throw ``HTTPException `` if the HTTP code returned is
276+ greater than or equal to 400.
277+
278+ If you want to see the response body, you can set ``http_errors `` to ``false `` to
279+ return the content instead:
275280
276281.. literalinclude :: curlrequest/026.php
277282
0 commit comments