A very basic WSGI Handler for Mongrel2
License
berry/Mongrel2-WSGI-Handler
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
master
Could not load branches
Nothing to show
Could not load tags
Nothing to show
{{ refName }}
default
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code
-
Clone
Use Git or checkout with SVN using the web URL.
Work fast with our official CLI. Learn more about the CLI.
- Open with GitHub Desktop
- Download ZIP
Sign In Required
Please sign in to use Codespaces.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching GitHub Desktop
If nothing happens, download GitHub Desktop and try again.
Launching Xcode
If nothing happens, download Xcode and try again.
Launching Visual Studio Code
Your codespace will open once ready.
There was a problem preparing your codespace, please try again.
Latest commit
Git stats
Files
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
## Basic WSGI Handler for Mongrel2 By: berry.groenendijk@gmail.com Date: 3 August 2010 This is a very basic WSGI Handler for Mongrel2 (http://mongrel2.org/home). It is based on SimpleHandler from de wsgi reference implementation in Python 2.6 or higher. The code currently handles a couple of simple WSGI application. It also handles a demo Django WSGI application, see http://github.com/berry/Django-demo. Known issues: - this wsgi handler currently doesn't support chunked responses. I haven't figured out yet how to do this. - [26 aug 2010] since mongrel2 1.0beta1 the wsgi handler doesn't cookies correctly. - [26 aug 2010] since mongrel2 1.0beta1 some HTTP posts cause a bad request error. Other HTTP posts do work however. - [26 aug 2010] since mongrel2 1.0beta1 redirects generated by Django will fail. - [3 sept 2010] HTTP_HOST header seems to be missing. Django expects it. Need to investigate. Status of the WSGI handler as of august 2010: only basic simple WSGI applications seems to work correctly. Fixed issues: - [FIXED 4 aug 2010] the handler does not handle query strings correctly right now. Still have to fix and test this. - [UGLY FIX 4 aug 2010 - Removing BOM(s) before returning the response] Using the Django demo app I get some strange HTML parsing errors in Chrome. It says "Extra <html> encountered...". Which leads to a couple a follow up parsing errors. It apparently has something to do with unicode and a BOM being present in the response data. Strange. Hmmm, the Django development server (./manage runserver) has the same problem.
About
A very basic WSGI Handler for Mongrel2
Resources
License
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published