More likely then to be an application issue than something with
mod_wsgi.
Beyond wrapping the WSGI entry point for Django and dumping out
request headers and response headers and confirming that any cookie
stuff is correct, not sure what to suggest.
Graham
On Nov 3, 11:23 am, "Tiger Uppercut"
> Is the login mechanism relying on web application form based
> submission, or relying on web server HTTP Basic authentication. If the
> latter, you must enable the directive:
>
> WSGIPassAuthorization On
>
> in Apache configuration for mod_wsgi, else the HTTP Basic auth
> information isn't
On Oct 30, 9:22 pm, "Tiger Uppercut" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I wasn't sure whether this was a djangoAMF issue or django, so apologies for
> the double posting.
>
> I'm having trouble using djangoAMF to communicate between my flex UI and my
> django site, django_wrapper.
>
> - My
Any thoughts on this one?
To summarize
- using djangoAMF
- want to login user through flex UI
- flex UI method calls function
authAndLoginVisitor(request,this_email,raw_password)
- authAndLoginVisitor calls login(request,this_user) once this_user with
this_email and raw_password is found in
Hi,
I wasn't sure whether this was a djangoAMF issue or django, so apologies for
the double posting.
I'm having trouble using djangoAMF to communicate between my flex UI and my
django site, django_wrapper.
- My django_wrapper is served at /main by mod_wsgi.
* The django code base is in
5 matches
Mail list logo
