django-urls

I use such Nginx configuration for the domain: server_name_in_redirect off; listen 80; server_name ~^(www\.)?(.+)$; root /var/www/$2/htdocs; location / { try_files $uri $uri/ $uri/index.htm @django; index index.html index.htm; } location @django { fastcgi_pass 127.0.0.1:8801; fastcgi_param PATH_INFO $fastcgi_script_name; fastcgi_param REQUEST_METHOD $request_method; fastcgi_param QUERY_STRING $query_string; fastcgi_param SERVER_NAME $server_name; fastcgi_param SERVER_PORT $server_port; fastcgi_param SERVER_PROTOCOL $server_protocol; fastcgi_param CONTENT_TYPE $content_type; fastcgi_param

It might be a silly question for many, but why can't I instead Create a view in django that takes a request and returns HttpResponse in, say, JSON format Map the view to a URL Hit the URL from my browser or another server and use the result? Thanks. EDIT - Two approaches: Import some djangorestframework or tastypie and build an api in my application which will throw json responses VS building a class based view and tell it to return json response . Is there any huge advantage of using the first one? I think you could make the same argument about any extension library. It just depends on how

I am trying to retrieve the absolute path (starting with http://) while calling a FileField at the template. How can I achieve this ? ie: {{fl.uploadedfile}} -> returns relative path like media/uploads/ while I want This Cheers The Django File object provides several convenience functions/attributes, one of which is the URL associated with the file. In this case, as you pointed out, you're looking for the url attribute. Just found the answer: adding .url fixes this issue fixes it such as {{fl.uploadedfile.url}} 来源： https://stackoverflow.com/questions/1211527/django-getting-the-absolute-path-of

I've already checked out the following stackoverflow question regarding the difference between HttpResponse, HttpResponseRedirect, and render_to_response , as well as having gone through the official django docs, but I'm really uncertain how best to get the functionality I'm looking to create. Right now I have an index.html with a login function (as seen in the views.py below) where the render_to_response that brings me to portal/index.html . However, as urls.py (see below) dictates, the url in the url bar of my browser is http://127.0.0.1:8000/login/ . This means that refreshing the page