forked from AFPy/python-docs-fr
582 lines
20 KiB
Plaintext
582 lines
20 KiB
Plaintext
# Copyright (C) 2001-2018, Python Software Foundation
|
|
# For licence information, see README file.
|
|
#
|
|
msgid ""
|
|
msgstr ""
|
|
"Project-Id-Version: Python 3\n"
|
|
"Report-Msgid-Bugs-To: \n"
|
|
"POT-Creation-Date: 2021-02-24 17:33+0100\n"
|
|
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
|
|
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
|
|
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
|
|
"Language: fr\n"
|
|
"MIME-Version: 1.0\n"
|
|
"Content-Type: text/plain; charset=UTF-8\n"
|
|
"Content-Transfer-Encoding: 8bit\n"
|
|
|
|
#: howto/urllib2.rst:5
|
|
msgid "HOWTO Fetch Internet Resources Using The urllib Package"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:0
|
|
msgid "Author"
|
|
msgstr "Auteur"
|
|
|
|
#: howto/urllib2.rst:7
|
|
msgid "`Michael Foord <http://www.voidspace.org.uk/python/index.shtml>`_"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:11
|
|
msgid ""
|
|
"There is a French translation of an earlier revision of this HOWTO, "
|
|
"available at `urllib2 - Le Manuel manquant <http://www.voidspace.org.uk/"
|
|
"python/articles/urllib2_francais.shtml>`_."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:18
|
|
msgid "Introduction"
|
|
msgstr "Introduction"
|
|
|
|
#: howto/urllib2.rst:22
|
|
msgid ""
|
|
"You may also find useful the following article on fetching web resources "
|
|
"with Python:"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:25
|
|
msgid ""
|
|
"`Basic Authentication <http://www.voidspace.org.uk/python/articles/"
|
|
"authentication.shtml>`_"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:27
|
|
msgid "A tutorial on *Basic Authentication*, with examples in Python."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:29
|
|
msgid ""
|
|
"**urllib.request** is a Python module for fetching URLs (Uniform Resource "
|
|
"Locators). It offers a very simple interface, in the form of the *urlopen* "
|
|
"function. This is capable of fetching URLs using a variety of different "
|
|
"protocols. It also offers a slightly more complex interface for handling "
|
|
"common situations - like basic authentication, cookies, proxies and so on. "
|
|
"These are provided by objects called handlers and openers."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:36
|
|
msgid ""
|
|
"urllib.request supports fetching URLs for many \"URL schemes\" (identified "
|
|
"by the string before the ``\":\"`` in URL - for example ``\"ftp\"`` is the "
|
|
"URL scheme of ``\"ftp://python.org/\"``) using their associated network "
|
|
"protocols (e.g. FTP, HTTP). This tutorial focuses on the most common case, "
|
|
"HTTP."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:41
|
|
msgid ""
|
|
"For straightforward situations *urlopen* is very easy to use. But as soon as "
|
|
"you encounter errors or non-trivial cases when opening HTTP URLs, you will "
|
|
"need some understanding of the HyperText Transfer Protocol. The most "
|
|
"comprehensive and authoritative reference to HTTP is :rfc:`2616`. This is a "
|
|
"technical document and not intended to be easy to read. This HOWTO aims to "
|
|
"illustrate using *urllib*, with enough detail about HTTP to help you "
|
|
"through. It is not intended to replace the :mod:`urllib.request` docs, but "
|
|
"is supplementary to them."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:51
|
|
msgid "Fetching URLs"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:53
|
|
msgid "The simplest way to use urllib.request is as follows::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:59
|
|
msgid ""
|
|
"If you wish to retrieve a resource via URL and store it in a temporary "
|
|
"location, you can do so via the :func:`shutil.copyfileobj` and :func:"
|
|
"`tempfile.NamedTemporaryFile` functions::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:74
|
|
msgid ""
|
|
"Many uses of urllib will be that simple (note that instead of an 'http:' URL "
|
|
"we could have used a URL starting with 'ftp:', 'file:', etc.). However, "
|
|
"it's the purpose of this tutorial to explain the more complicated cases, "
|
|
"concentrating on HTTP."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:79
|
|
msgid ""
|
|
"HTTP is based on requests and responses - the client makes requests and "
|
|
"servers send responses. urllib.request mirrors this with a ``Request`` "
|
|
"object which represents the HTTP request you are making. In its simplest "
|
|
"form you create a Request object that specifies the URL you want to fetch. "
|
|
"Calling ``urlopen`` with this Request object returns a response object for "
|
|
"the URL requested. This response is a file-like object, which means you can "
|
|
"for example call ``.read()`` on the response::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:93
|
|
msgid ""
|
|
"Note that urllib.request makes use of the same Request interface to handle "
|
|
"all URL schemes. For example, you can make an FTP request like so::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:98
|
|
msgid ""
|
|
"In the case of HTTP, there are two extra things that Request objects allow "
|
|
"you to do: First, you can pass data to be sent to the server. Second, you "
|
|
"can pass extra information (\"metadata\") *about* the data or about the "
|
|
"request itself, to the server - this information is sent as HTTP \"headers"
|
|
"\". Let's look at each of these in turn."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:105
|
|
msgid "Data"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:107
|
|
msgid ""
|
|
"Sometimes you want to send data to a URL (often the URL will refer to a CGI "
|
|
"(Common Gateway Interface) script or other web application). With HTTP, this "
|
|
"is often done using what's known as a **POST** request. This is often what "
|
|
"your browser does when you submit a HTML form that you filled in on the web. "
|
|
"Not all POSTs have to come from forms: you can use a POST to transmit "
|
|
"arbitrary data to your own application. In the common case of HTML forms, "
|
|
"the data needs to be encoded in a standard way, and then passed to the "
|
|
"Request object as the ``data`` argument. The encoding is done using a "
|
|
"function from the :mod:`urllib.parse` library. ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:131
|
|
msgid ""
|
|
"Note that other encodings are sometimes required (e.g. for file upload from "
|
|
"HTML forms - see `HTML Specification, Form Submission <https://www.w3.org/TR/"
|
|
"REC-html40/interact/forms.html#h-17.13>`_ for more details)."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:136
|
|
msgid ""
|
|
"If you do not pass the ``data`` argument, urllib uses a **GET** request. One "
|
|
"way in which GET and POST requests differ is that POST requests often have "
|
|
"\"side-effects\": they change the state of the system in some way (for "
|
|
"example by placing an order with the website for a hundredweight of tinned "
|
|
"spam to be delivered to your door). Though the HTTP standard makes it clear "
|
|
"that POSTs are intended to *always* cause side-effects, and GET requests "
|
|
"*never* to cause side-effects, nothing prevents a GET request from having "
|
|
"side-effects, nor a POST requests from having no side-effects. Data can also "
|
|
"be passed in an HTTP GET request by encoding it in the URL itself."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:146
|
|
msgid "This is done as follows::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:161
|
|
msgid ""
|
|
"Notice that the full URL is created by adding a ``?`` to the URL, followed "
|
|
"by the encoded values."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:165
|
|
msgid "Headers"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:167
|
|
msgid ""
|
|
"We'll discuss here one particular HTTP header, to illustrate how to add "
|
|
"headers to your HTTP request."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:170
|
|
msgid ""
|
|
"Some websites [#]_ dislike being browsed by programs, or send different "
|
|
"versions to different browsers [#]_. By default urllib identifies itself as "
|
|
"``Python-urllib/x.y`` (where ``x`` and ``y`` are the major and minor version "
|
|
"numbers of the Python release, e.g. ``Python-urllib/2.5``), which may "
|
|
"confuse the site, or just plain not work. The way a browser identifies "
|
|
"itself is through the ``User-Agent`` header [#]_. When you create a Request "
|
|
"object you can pass a dictionary of headers in. The following example makes "
|
|
"the same request as above, but identifies itself as a version of Internet "
|
|
"Explorer [#]_. ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:197
|
|
msgid ""
|
|
"The response also has two useful methods. See the section on `info and "
|
|
"geturl`_ which comes after we have a look at what happens when things go "
|
|
"wrong."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:202
|
|
msgid "Handling Exceptions"
|
|
msgstr "Gestion des exceptions"
|
|
|
|
#: howto/urllib2.rst:204
|
|
msgid ""
|
|
"*urlopen* raises :exc:`URLError` when it cannot handle a response (though as "
|
|
"usual with Python APIs, built-in exceptions such as :exc:`ValueError`, :exc:"
|
|
"`TypeError` etc. may also be raised)."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:208
|
|
msgid ""
|
|
":exc:`HTTPError` is the subclass of :exc:`URLError` raised in the specific "
|
|
"case of HTTP URLs."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:211
|
|
msgid "The exception classes are exported from the :mod:`urllib.error` module."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:214
|
|
msgid "URLError"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:216
|
|
msgid ""
|
|
"Often, URLError is raised because there is no network connection (no route "
|
|
"to the specified server), or the specified server doesn't exist. In this "
|
|
"case, the exception raised will have a 'reason' attribute, which is a tuple "
|
|
"containing an error code and a text error message."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:221
|
|
msgid "e.g. ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:232
|
|
msgid "HTTPError"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:234
|
|
msgid ""
|
|
"Every HTTP response from the server contains a numeric \"status code\". "
|
|
"Sometimes the status code indicates that the server is unable to fulfil the "
|
|
"request. The default handlers will handle some of these responses for you "
|
|
"(for example, if the response is a \"redirection\" that requests the client "
|
|
"fetch the document from a different URL, urllib will handle that for you). "
|
|
"For those it can't handle, urlopen will raise an :exc:`HTTPError`. Typical "
|
|
"errors include '404' (page not found), '403' (request forbidden), and "
|
|
"'401' (authentication required)."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:242
|
|
msgid ""
|
|
"See section 10 of :rfc:`2616` for a reference on all the HTTP error codes."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:244
|
|
msgid ""
|
|
"The :exc:`HTTPError` instance raised will have an integer 'code' attribute, "
|
|
"which corresponds to the error sent by the server."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:248
|
|
msgid "Error Codes"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:250
|
|
msgid ""
|
|
"Because the default handlers handle redirects (codes in the 300 range), and "
|
|
"codes in the 100--299 range indicate success, you will usually only see "
|
|
"error codes in the 400--599 range."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:254
|
|
msgid ""
|
|
":attr:`http.server.BaseHTTPRequestHandler.responses` is a useful dictionary "
|
|
"of response codes in that shows all the response codes used by :rfc:`2616`. "
|
|
"The dictionary is reproduced here for convenience ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:326
|
|
msgid ""
|
|
"When an error is raised the server responds by returning an HTTP error code "
|
|
"*and* an error page. You can use the :exc:`HTTPError` instance as a response "
|
|
"on the page returned. This means that as well as the code attribute, it also "
|
|
"has read, geturl, and info, methods as returned by the ``urllib.response`` "
|
|
"module::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:346
|
|
msgid "Wrapping it Up"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:348
|
|
msgid ""
|
|
"So if you want to be prepared for :exc:`HTTPError` *or* :exc:`URLError` "
|
|
"there are two basic approaches. I prefer the second approach."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:352
|
|
msgid "Number 1"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:374
|
|
msgid ""
|
|
"The ``except HTTPError`` *must* come first, otherwise ``except URLError`` "
|
|
"will *also* catch an :exc:`HTTPError`."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:378
|
|
msgid "Number 2"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:399
|
|
msgid "info and geturl"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:401
|
|
msgid ""
|
|
"The response returned by urlopen (or the :exc:`HTTPError` instance) has two "
|
|
"useful methods :meth:`info` and :meth:`geturl` and is defined in the module :"
|
|
"mod:`urllib.response`.."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:405
|
|
msgid ""
|
|
"**geturl** - this returns the real URL of the page fetched. This is useful "
|
|
"because ``urlopen`` (or the opener object used) may have followed a "
|
|
"redirect. The URL of the page fetched may not be the same as the URL "
|
|
"requested."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:409
|
|
msgid ""
|
|
"**info** - this returns a dictionary-like object that describes the page "
|
|
"fetched, particularly the headers sent by the server. It is currently an :"
|
|
"class:`http.client.HTTPMessage` instance."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:413
|
|
msgid ""
|
|
"Typical headers include 'Content-length', 'Content-type', and so on. See the "
|
|
"`Quick Reference to HTTP Headers <http://jkorpela.fi/http.html>`_ for a "
|
|
"useful listing of HTTP headers with brief explanations of their meaning and "
|
|
"use."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:420
|
|
msgid "Openers and Handlers"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:422
|
|
msgid ""
|
|
"When you fetch a URL you use an opener (an instance of the perhaps "
|
|
"confusingly-named :class:`urllib.request.OpenerDirector`). Normally we have "
|
|
"been using the default opener - via ``urlopen`` - but you can create custom "
|
|
"openers. Openers use handlers. All the \"heavy lifting\" is done by the "
|
|
"handlers. Each handler knows how to open URLs for a particular URL scheme "
|
|
"(http, ftp, etc.), or how to handle an aspect of URL opening, for example "
|
|
"HTTP redirections or HTTP cookies."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:430
|
|
msgid ""
|
|
"You will want to create openers if you want to fetch URLs with specific "
|
|
"handlers installed, for example to get an opener that handles cookies, or to "
|
|
"get an opener that does not handle redirections."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:434
|
|
msgid ""
|
|
"To create an opener, instantiate an ``OpenerDirector``, and then call ``."
|
|
"add_handler(some_handler_instance)`` repeatedly."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:437
|
|
msgid ""
|
|
"Alternatively, you can use ``build_opener``, which is a convenience function "
|
|
"for creating opener objects with a single function call. ``build_opener`` "
|
|
"adds several handlers by default, but provides a quick way to add more and/"
|
|
"or override the default handlers."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:442
|
|
msgid ""
|
|
"Other sorts of handlers you might want to can handle proxies, "
|
|
"authentication, and other common but slightly specialised situations."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:445
|
|
msgid ""
|
|
"``install_opener`` can be used to make an ``opener`` object the (global) "
|
|
"default opener. This means that calls to ``urlopen`` will use the opener you "
|
|
"have installed."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:449
|
|
msgid ""
|
|
"Opener objects have an ``open`` method, which can be called directly to "
|
|
"fetch urls in the same way as the ``urlopen`` function: there's no need to "
|
|
"call ``install_opener``, except as a convenience."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:455
|
|
msgid "Basic Authentication"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:457
|
|
msgid ""
|
|
"To illustrate creating and installing a handler we will use the "
|
|
"``HTTPBasicAuthHandler``. For a more detailed discussion of this subject -- "
|
|
"including an explanation of how Basic Authentication works - see the `Basic "
|
|
"Authentication Tutorial <http://www.voidspace.org.uk/python/articles/"
|
|
"authentication.shtml>`_."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:463
|
|
msgid ""
|
|
"When authentication is required, the server sends a header (as well as the "
|
|
"401 error code) requesting authentication. This specifies the "
|
|
"authentication scheme and a 'realm'. The header looks like: ``WWW-"
|
|
"Authenticate: SCHEME realm=\"REALM\"``."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:468
|
|
msgid "e.g."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:475
|
|
msgid ""
|
|
"The client should then retry the request with the appropriate name and "
|
|
"password for the realm included as a header in the request. This is 'basic "
|
|
"authentication'. In order to simplify this process we can create an instance "
|
|
"of ``HTTPBasicAuthHandler`` and an opener to use this handler."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:480
|
|
msgid ""
|
|
"The ``HTTPBasicAuthHandler`` uses an object called a password manager to "
|
|
"handle the mapping of URLs and realms to passwords and usernames. If you "
|
|
"know what the realm is (from the authentication header sent by the server), "
|
|
"then you can use a ``HTTPPasswordMgr``. Frequently one doesn't care what the "
|
|
"realm is. In that case, it is convenient to use "
|
|
"``HTTPPasswordMgrWithDefaultRealm``. This allows you to specify a default "
|
|
"username and password for a URL. This will be supplied in the absence of you "
|
|
"providing an alternative combination for a specific realm. We indicate this "
|
|
"by providing ``None`` as the realm argument to the ``add_password`` method."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:490
|
|
msgid ""
|
|
"The top-level URL is the first URL that requires authentication. URLs "
|
|
"\"deeper\" than the URL you pass to .add_password() will also match. ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:515
|
|
msgid ""
|
|
"In the above example we only supplied our ``HTTPBasicAuthHandler`` to "
|
|
"``build_opener``. By default openers have the handlers for normal situations "
|
|
"-- ``ProxyHandler`` (if a proxy setting such as an :envvar:`http_proxy` "
|
|
"environment variable is set), ``UnknownHandler``, ``HTTPHandler``, "
|
|
"``HTTPDefaultErrorHandler``, ``HTTPRedirectHandler``, ``FTPHandler``, "
|
|
"``FileHandler``, ``DataHandler``, ``HTTPErrorProcessor``."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:522
|
|
msgid ""
|
|
"``top_level_url`` is in fact *either* a full URL (including the 'http:' "
|
|
"scheme component and the hostname and optionally the port number) e.g. ``"
|
|
"\"http://example.com/\"`` *or* an \"authority\" (i.e. the hostname, "
|
|
"optionally including the port number) e.g. ``\"example.com\"`` or ``"
|
|
"\"example.com:8080\"`` (the latter example includes a port number). The "
|
|
"authority, if present, must NOT contain the \"userinfo\" component - for "
|
|
"example ``\"joe:password@example.com\"`` is not correct."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:532
|
|
msgid "Proxies"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:534
|
|
msgid ""
|
|
"**urllib** will auto-detect your proxy settings and use those. This is "
|
|
"through the ``ProxyHandler``, which is part of the normal handler chain when "
|
|
"a proxy setting is detected. Normally that's a good thing, but there are "
|
|
"occasions when it may not be helpful [#]_. One way to do this is to setup "
|
|
"our own ``ProxyHandler``, with no proxies defined. This is done using "
|
|
"similar steps to setting up a `Basic Authentication`_ handler: ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:547
|
|
msgid ""
|
|
"Currently ``urllib.request`` *does not* support fetching of ``https`` "
|
|
"locations through a proxy. However, this can be enabled by extending urllib."
|
|
"request as shown in the recipe [#]_."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:553
|
|
msgid ""
|
|
"``HTTP_PROXY`` will be ignored if a variable ``REQUEST_METHOD`` is set; see "
|
|
"the documentation on :func:`~urllib.request.getproxies`."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:558
|
|
msgid "Sockets and Layers"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:560
|
|
msgid ""
|
|
"The Python support for fetching resources from the web is layered. urllib "
|
|
"uses the :mod:`http.client` library, which in turn uses the socket library."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:563
|
|
msgid ""
|
|
"As of Python 2.3 you can specify how long a socket should wait for a "
|
|
"response before timing out. This can be useful in applications which have to "
|
|
"fetch web pages. By default the socket module has *no timeout* and can hang. "
|
|
"Currently, the socket timeout is not exposed at the http.client or urllib."
|
|
"request levels. However, you can set the default timeout globally for all "
|
|
"sockets using ::"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:586
|
|
msgid "Footnotes"
|
|
msgstr "Notes"
|
|
|
|
#: howto/urllib2.rst:588
|
|
msgid "This document was reviewed and revised by John Lee."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:590
|
|
msgid "Google for example."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:591
|
|
msgid ""
|
|
"Browser sniffing is a very bad practice for website design - building sites "
|
|
"using web standards is much more sensible. Unfortunately a lot of sites "
|
|
"still send different versions to different browsers."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:594
|
|
msgid ""
|
|
"The user agent for MSIE 6 is *'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT "
|
|
"5.1; SV1; .NET CLR 1.1.4322)'*"
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:596
|
|
msgid ""
|
|
"For details of more HTTP request headers, see `Quick Reference to HTTP "
|
|
"Headers`_."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:598
|
|
msgid ""
|
|
"In my case I have to use a proxy to access the internet at work. If you "
|
|
"attempt to fetch *localhost* URLs through this proxy it blocks them. IE is "
|
|
"set to use the proxy, which urllib picks up on. In order to test scripts "
|
|
"with a localhost server, I have to prevent urllib from using the proxy."
|
|
msgstr ""
|
|
|
|
#: howto/urllib2.rst:603
|
|
msgid ""
|
|
"urllib opener for SSL proxy (CONNECT method): `ASPN Cookbook Recipe <https://"
|
|
"code.activestate.com/recipes/456195/>`_."
|
|
msgstr ""
|