On Mon, May 25, 2009 at 1:32 PM, notcourage <klr...@gmail.com> wrote:
>
> @require_GET
> def forbiddenView(request):
> return HttpResponseForbidden()
>
So the login requirement isn't directly decorating the view. It's still
there somewhere, based on your curl results. Given this view:
from django.views.decorators.http import require_GET
from django.http import HttpResponseForbidden
@require_GET
def testit(request):
return HttpResponseForbidden()
and this url pattern:
from ttt.views import testit
urlpatterns = patterns('',
(r'^testit/', testit),
}
I see:
D:\>curl -v http://localhost:8888/testit/
* About to connect() to localhost port 8888 (#0)
* Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 8888 (#0)
> GET /testit/ HTTP/1.1
> User-Agent: curl/7.19.5 (i586-pc-mingw32msvc) libcurl/7.19.5 zlib/1.2.3
> Host: localhost:8888
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 403 FORBIDDEN
< Date: Mon, 25 May 2009 19:43:41 GMT
< Server: WSGIServer/0.1 Python/2.5.2
< Content-Type: text/html; charset=utf-8
<
* Closing connection #0
Leaving the view unchanged but changing the urlpatterns to:
from django.contrib.auth.decorators import login_required
from ttt.views import testit
urlpatterns = patterns('',
(r'^testit/', login_required(testit)),
)
I then see from curl:
* About to connect() to localhost port 8888 (#0)
* Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 8888 (#0)
> GET /testit/ HTTP/1.1
> User-Agent: curl/7.19.5 (i586-pc-mingw32msvc) libcurl/7.19.5 zlib/1.2.3
> Host: localhost:8888
> Accept: */*
>
* HTTP 1.0, assume close after body
< HTTP/1.0 302 FOUND
< Date: Mon, 25 May 2009 19:45:48 GMT
< Server: WSGIServer/0.1 Python/2.5.2
< Vary: Cookie
< Content-Type: text/html; charset=utf-8
< Location: http://localhost:8888/accounts/login/?next=/testit/
<
* Closing connection #0
So showing that your view isn't decorated with login_required doesn't prove
anything. Something in your setup (urls, middleware, I don't know) is
requiring a login for that view, and preventing you from even getting to the
'return HttpResponseForbidden()'.
Karen
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
