repoze.urchin README
This package provides WSGI middleware for injecting the markup required to use Google Analytics into web pages.
Please see docs/index.rst for detailed documentation.
repoze.urchin Changelog
0.2 (2011-10-10)
Replaced urchin javascript with new async tracking code. See:
http://www.google.com/support/googleanalytics/bin/answer.py?answer=174090
Note that the script is now inserted at the end of the <head> tag.
Added bypass for HEAD requests. This is a workaround for an assertion in webob.Response that doesn’t let you set the body on a response if the request method is ‘HEAD’. This behavior on the part of webob is actually bogus, as outlined here:
http://blog.dscpl.com.au/2009/10/wsgi-issues-with-http-head-requests.html
The key issue here is that as long as anything in the WSGI stack tries to special case ‘HEAD’ requests, we can end up with responses with headers which differ depending on whether the request method is ‘GET’ or ‘HEAD’. In this specific example, by bypassing the urchin processing in the event of a HEAD request, we wind up with a Content-Length header for HEAD that doesn’t include the extra bytes for the inserted urchin code that we would get with a GET request. This is, by definition of the standards, wrong, and yet unavoidable as long as webob is in our stack.
For now, we can hold our noses and know that probably nothing’s going to really break because of this discrepency, but we can maybe try to convince the webob crowd to drop conditional processing for HEAD requests.
0.1 (2009-06-02)
Initial release.
Metadata
Release files for repoze.urchin 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| repoze.urchin-0.2.tar.gz | 17.2 kB | Without provenance | Details for repoze.urchin-0.2.tar.gz |
Release files / repoze.urchin-0.2.tar.gz
| Download URL | repoze.urchin-0.2.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6563f739ba172ee87846bd673c564dd1213517044d2e7d617be3e08a0295b72a
|
|
BLAKE2b-256 checksum How to use checksums |
c6367749eadc9bbd384fa496eb068c20bc4d0ff5aa1d308004da095692e29d4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for repoze.urchin 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.