Home
last modified time | relevance | path

Searched refs:PATH_INFO (Results 1 – 12 of 12) sorted by relevance

/external/autotest/frontend/
Dfrontend.wsgi22 environ['PATH_INFO'] = environ['SCRIPT_NAME'] + environ['PATH_INFO']
/external/chromium-trace/catapult/third_party/Paste/docs/
Durl-parsing-with-wsgi.txt45 in particular relate to URLs -- ``SCRIPT_NAME`` and ``PATH_INFO`` --
117 When a request comes in, the parser looks at ``PATH_INFO`` to see
125 URLParser serves directories. When ``PATH_INFO`` is empty, that
138 Otherwise we get a string like ``/path...``. Note that ``PATH_INFO``
142 ``PATH_INFO`` is ``/blog/edit/285``, then the first part is ``blog``.
143 It appends this to ``SCRIPT_NAME``, and strips it off ``PATH_INFO``
226 first, rest = wsgilib.path_info_split(environ['PATH_INFO'])
Ddo-it-yourself-framework.txt18 Explain SCRIPT_NAME/PATH_INFO better
51 we got here) and ``PATH_INFO`` (what we have left).
174 ``PATH_INFO``. ``SCRIPT_NAME`` is everything that was used up
175 *getting here*. ``PATH_INFO`` is everything left over -- it's
191 path_info = environ.get('PATH_INFO', '')
195 # PATH_INFO always starts with a /, so we'll get rid of it:
210 # Now fix up SCRIPT_NAME and PATH_INFO...
212 environ['PATH_INFO'] = rest
Dnews.txt242 * Fixed bug in paste lint where PATH_INFO would become unicode.
534 ``SCRIPT_NAME`` and ``PATH_INFO``, as specified in the CGI spec.
/external/chromium-trace/catapult/third_party/WebOb/docs/
Dcomment-example.txt266 ``SCRIPT_NAME`` and ``PATH_INFO``. Everything in ``SCRIPT_NAME`` has
267 already been parsed, and everything in ``PATH_INFO`` has yet to be
268 parsed. That means that the URL *without* ``PATH_INFO`` is the path
271 ``PATH_INFO`` is ``req.application_url``. We have to capture it early
273 wrapping may update ``SCRIPT_NAME`` and ``PATH_INFO``).
Dnews.txt293 with raw SCRIPT_NAME and PATH_INFO values, which caused nonsensical
298 decode the raw WSGI PATH_INFO and SCRIPT_NAME variables when the
302 ``url_encoding``. ``url_encoding`` will be used to decode PATH_INFO and
306 PATH_INFO and SCRIPT_NAME.
353 of SCRIPT_NAME and PATH_INFO.
Ddo-it-yourself.txt32 …]`` (which is the path leading *up to* the application), and ``environ['PATH_INFO']`` (the remaini…
220 …t itself a WSGI application. So when a request comes in, it looks at ``PATH_INFO`` (also known as…
256 …r expression against ``req.path_info``. This is the same as ``environ['PATH_INFO']``. That's all…
Dreference.txt67 'PATH_INFO': '/article',
152 path segment on PATH_INFO:
889 PATH_INFO: '/'
Dwiki-example.txt276 URLs, PATH_INFO, and SCRIPT_NAME
299 and ``PATH_INFO``. ``req.script_name`` points to the *application*.
Dindex.txt136 path, not PATH_INFO). E.g., ``'http://localhost/app-root'``
/external/chromium-trace/catapult/third_party/Paste/paste/auth/
Ddigest.py137 fullpath = url_quote(SCRIPT_NAME(environ)) + url_quote(PATH_INFO(environ))
/external/chromium-trace/catapult/third_party/Paste/paste/
Dhttpheaders.py172 PATH_INFO = EnvironVariable("PATH_INFO") variable