<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://brwiki2.brulescorp.com/brwiki2/index.php?action=history&amp;feed=atom&amp;title=Control_statements</id>
	<title>Control statements - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://brwiki2.brulescorp.com/brwiki2/index.php?action=history&amp;feed=atom&amp;title=Control_statements"/>
	<link rel="alternate" type="text/html" href="https://brwiki2.brulescorp.com/brwiki2/index.php?title=Control_statements&amp;action=history"/>
	<updated>2026-04-29T20:34:09Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://brwiki2.brulescorp.com/brwiki2/index.php?title=Control_statements&amp;diff=6893&amp;oldid=prev</id>
		<title>Laura: Created page with &quot;As of 4.2  These are case insensitive.  &#039;&#039;&#039;USER-AGENT&#039;&#039;&#039;  string  Specify  the  User-Agent  string to send to the HTTP server. Some badly done CGIs fail if its  not  set to &quot;M...&quot;</title>
		<link rel="alternate" type="text/html" href="https://brwiki2.brulescorp.com/brwiki2/index.php?title=Control_statements&amp;diff=6893&amp;oldid=prev"/>
		<updated>2013-08-08T15:55:53Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;As of 4.2  These are case insensitive.  &amp;#039;&amp;#039;&amp;#039;USER-AGENT&amp;#039;&amp;#039;&amp;#039;  string  Specify  the  User-Agent  string to send to the HTTP server. Some badly done CGIs fail if its  not  set to &amp;quot;M...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;As of 4.2&lt;br /&gt;
&lt;br /&gt;
These are case insensitive.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;USER-AGENT&amp;#039;&amp;#039;&amp;#039;  string&lt;br /&gt;
&lt;br /&gt;
Specify  the  User-Agent  string to send to the HTTP server. Some badly done CGIs fail if its  not  set to &amp;quot;Mozilla/4.0&amp;quot;.  To encode blanks in the string, surround the string with single quote marks.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;REFERER&amp;#039;&amp;#039;&amp;#039;    the linked-from URL&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;COOKIE&amp;#039;&amp;#039;&amp;#039;  “NAME=data”&lt;br /&gt;
&lt;br /&gt;
e. g. “NAME1=value1; NAME2=value2&amp;quot; &lt;br /&gt;
&lt;br /&gt;
If  no &amp;#039;=&amp;#039; letter is used in the line, it is treated as a filename used to read  previously stored cookie lines from, which should be used in this session if they match.  Using this method also activates the &amp;quot;cookie parser&amp;quot; which will record incoming cookies too, which may be handy if you&amp;#039;re using this in combination with the -L/--location option. The file format of the file to read cookies from should be plain HTTP headers or the Netscape/Mozilla cookie file format.&lt;br /&gt;
&lt;br /&gt;
NOTE that the file specified with COOKIE is only used as input. No cookies will be stored in the file. To store cookies, save the HTTP headers to a file using DUMP-HEADER.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;COOKIE-JAR&amp;#039;&amp;#039;&amp;#039;    filename&lt;br /&gt;
&lt;br /&gt;
The name of a file that is to contain a copy of all cookies encountered either inbound or outbound.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;DATA&amp;#039;&amp;#039;&amp;#039;    filename&lt;br /&gt;
&lt;br /&gt;
Sends  the  specified data in a POST request to the HTTP server, in a way that can emulate as if a user has  filled  in a HTML form and pressed the submit button. The data is sent exactly as specified with all newlines cut off. It is expected to  be  &amp;quot;url-encoded&amp;quot;.  This  will cause curl  to  pass  the data to the server using the content-type application/x-www-form-urlencoded. If more than one DATA option is used on the same command line, the data pieces  specified  will  be merged together with a separating semicolon. Thus, using &amp;#039;DATA name=daniel skill=great&amp;#039; would generate a post chunk that looks like &amp;#039;name=daniel&amp;amp;amp;skill=great&amp;#039;. &lt;br /&gt;
&lt;br /&gt;
If  you  start  the  data  with  the letter @, the rest should be a file name to read the data from.  The contents of the file must already be url-encoded. Multiple files  can  also be specified. Posting data from a file named &amp;#039;footbar&amp;#039; would thus be done  with  &amp;quot;DATA  @footbar&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;HEADER&amp;#039;&amp;#039;&amp;#039; additional header parameters&lt;br /&gt;
&lt;br /&gt;
Extra header to use when getting a web page. You may specify any number of extra headers.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;DUMP-HEADERS&amp;#039;&amp;#039;&amp;#039; filename&lt;br /&gt;
&lt;br /&gt;
Write the HTTP headers to this file.&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;HEAD&amp;#039;&amp;#039;&amp;#039; – retrieve headers only&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SSLV2&amp;#039;&amp;#039;&amp;#039; -  force SSL version 2&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;SSLV3&amp;#039;&amp;#039;&amp;#039; -  force SSL version 3&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;WRITE-OUT&amp;#039;&amp;#039;&amp;#039; string&lt;br /&gt;
&lt;br /&gt;
Used with the following optional substitution values:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;url_effective&amp;lt;/B&amp;gt;  The URL that was fetched last.  &lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;http_code&amp;lt;/B&amp;gt;  The numerical code that was found in the last retrieved HTTP(S) page.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;time_total&amp;lt;/B&amp;gt;  The  total  time, in seconds, that the full operation lasted. The time will  be displayed with millisecond resolution.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;time_namelookup&amp;lt;/B&amp;gt;  The  time, in seconds, it took from the start until the name resolving was completed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;time_connect&amp;lt;/B&amp;gt;   The  time, in seconds, it took from the start until the connect to the remote host (or proxy) was completed.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;time_pretransfer&amp;lt;/B&amp;gt;  The time, in seconds, it took from the start until the file transfer is just about to begin. This includes all pre-transfer commands and negotiations that are specific to the particular protocol(s) involved.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;time_starttransfer&amp;lt;/B&amp;gt;  The time, in seconds, it took  from the start until the first byte is just about to be transferred. This includes time_pretransfer  and also the time the server needs to calculate the result. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;size_download&amp;lt;/B&amp;gt; The total amount of bytes that were downloaded.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;size_upload&amp;lt;/B&amp;gt; The total amount of bytes that were uploaded.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;size_header&amp;lt;/B&amp;gt; The total amount of bytes of the downloaded headers.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;size_request&amp;lt;/B&amp;gt; The total amount of bytes that were sent in the HTTP request.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;speed_download&amp;lt;/B&amp;gt; The average download speed that BR measured for the complete download.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;speed_upload&amp;lt;/B&amp;gt; The average upload speed that BR measured for the complete upload.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;B&amp;gt;content_type&amp;lt;/B&amp;gt;  The Content-Type of the requested  document, if there was any.&lt;/div&gt;</summary>
		<author><name>Laura</name></author>
	</entry>
</feed>