On Fri, 2007-11-16 at 19:19 -0800, [EMAIL PROTECTED] wrote: > > > On Nov 17, 4:15 am, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: > > On Fri, 2007-11-16 at 19:04 -0800, [EMAIL PROTECTED] wrote: > > > > [...] > > > > > Is there a way to have access to exactly the url used for the request? > > > > Seehttp://www.djangoproject.com/documentation/request_response/#methods > > > > Looking at the documentation for the "request" object would seem to be > > an obvious first place to look here. And, sure enough, get_full_path() > > is documented there. > > > > Malcolm > > > > -- > > Honk if you love peace and quiet.http://www.pointy-stick.com/blog/ > > That's where I started but if I do a request for > www.example.com/test/? > the get_full_path() returns > www.example.com/test/ > which isn't what we are needing in this situation, I am looking for > exactly what was requested through the url.
Ah, I see. Then you're doomed. The interface to the web server might not be passing through enough information for this to be determined. So any way to do this is going to be very dependent on how you are interacting with the web server. Try poking around inside request._req if you're using mod_python or request.environ if you're using the WSGI handler and maybe you'll get lucky, but I doubt it (particularly with WSGI, you're not going to be able to tell the difference between an empty query string and an omitted query string). Malcolm -- Atheism is a non-prophet organization. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
