在Django中将变量从Template转换为View的更有效的方法是什么？ | go中将变量从Template转换为View的更有效的方法是什么

本文介绍了在Django中将变量从Template转换为View的更有效的方法是什么？的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我的问题涉及将变量从模板传递到Django中查看。

我知道在URL和表单中传递变量。我遇到的第一个问题是，url可以被操纵，这不是我想要的。有没有办法阻止？

现在这是我作为一个帮助：

 < form action =/ match /method =post> 
 {％csrf_token％} 
 
< input type =hiddenname =name1value ={{male_results}}> 
< input type =hiddenname =userid1value ={{male_pic_userid}}> 
 
< input type =hiddenname =name2value ={{female_results}}> 
< input type =hiddenname =userid2value ={{female_pic_userid}}> 
 
< input type =submitvalue =提交/> 
< / form>

有没有办法避免使用这个？谢谢！

解决方案

大概有3种方式来保持这种信息：

会话（我对你的情况的建议）

只需将您想要的数据填入 request.session 字典;它将持续每个用户，您可以轻松访问：

 ＃view1 
 request.session [' name1'] = male_results 
 request.session ['userid1'] = male_pic_userid 
 
＃view2（或view1中的其他地方）
 male_results = request.session.get（'name1' ）
 male_pic_userid = request.session.get（'userid1'）

优点

您的模板不需要更改（除了删除现在不必要的表单）。

清除URL
即使关闭并重新打开浏览器窗口仍然保持

您不需要担心用户修改甚至看到会话数据更安全）

缺点

As使用 POST ，页面内容由URL 和会话数据指定 - URL不再是唯一的，用户无法共享特定页面依靠会话信息

查询参数

类似于 / match /？name1 = foo1& userid1&安培;名称2 =棒&安培; userid2 = 2 。您可以手动添加（< a href ='/ match /？name1 = {{male_results}} ... ）或更改您的 $ GET 。

 
 
 优点
 
 
  
 这些URL可以共享和加书签;如果它是一个带有过滤选项的列表，这可能是可取的（这里是我喜欢的汽车列表发布到Facebook，等。
 
 
 
 
 缺点
 
 
  
 正如您已经注意到的，这些可以由用户自由修改
 
 将这些添加到每个URL是一个巨大的痛苦
 
 
 
 
  POST表单（您当前的方法）
 
 
 优点
 
 
  
 一点隐藏（没有用户可见没有某种浏览器扩展）
 
 稍微更难操纵（尽管不要依赖于这种安全隐私）
 
 清洁网址
 
 
 
 
 缺点
 
 
  
 导致互联网上的此页面已过期资源管理器，如果您使用浏览器的返回按钮... 
 
  ...和您确定要重新发送此数据消息在大多数浏览器上，如果用户尝试重新加载您的任何网页
 
 如果用户重新打开页面（例如在URL栏中按返回），则所有这些状态信息将丢失。
 
 用户无法共享他们正在查看的确切页面;内容部分由非用户可见信息确定
 
 向每个导航操作添加 POST 数据是一个巨大的痛苦。
 
 
 
My question involves passing variables from the template to view in Django.
I know of passing variables in the URL and through a form. The problem I have with the first one is that the url could be manipulated which is not what I want. Is there anyway to prevent that?
Right now this is what I have as a band-aid:
<form action="/match/" method="post">
{% csrf_token %}

<input type="hidden" name="name1" value="{{ male_results }}">
<input type="hidden" name="userid1" value="{{ male_pic_userid }}">

<input type="hidden" name="name2" value="{{ female_results }}">
<input type="hidden" name="userid2" value="{{ female_pic_userid }}">

<input type="submit" value="Submit" />
</form>
Is there a way to avoid having to use this? Thank you!
 解决方案 
There are broadly 3 ways to hold onto this kind of information:
Session (my suggestion for your situation)
Just stuff the data you want into the request.session dictionary; it'll persist per-user, and you can access it easily:
# view1
request.session['name1'] = male_results
request.session['userid1'] = male_pic_userid

# view2 (or elsewhere in view1)
male_results = request.session.get('name1')
male_pic_userid = request.session.get('userid1')
Advantages
No changes needed to your templates (except removing your now-unnecessary forms).
Clean URLs
Persists even through closing and re-opening the browser window
You don't need to worry about users modifying or even seeing the session data (it's way more secure)
Disadvantages
As with POST, page content is dictated by the URL and session data — URLs are no longer unique, and users can't share a particular page that relies on session info
Query parameters
Something like /match/?name1=foo1&userid1&name2=bar&userid2=2. You can either add these manually (<a href='/match/?name1={{ male_results }}...) or by changing your POST form to GET.
Advantages
These URLs can be shared and bookmarked; if it's a list with filtering options, this is probably desirable ("Here's the list of cars I like" posted to Facebook, etc.)
Disadvantages
As you've already noted, these can be freely modified by the user
Adding these to every URL is a massive pain
POST form (your current approach)
Advantages
A little more hidden (nothing user-visible without some kind of browser extension)
Slightly harder to manipulate (though don't rely on this security-through-obscurity)
Cleaner URLs
Disdvantages
Leads to "this page has expired" messages on Internet Explorer if you use your browser's "back" button ...
... and "Are you sure you want to re-send this data" messages on most browsers if users try to reload any of your pages
All this state information will be lost if a user re-opens the page (pressing "return" in the URL bar, for instance)
Users can't share the exact page they're looking at; the content is partly determined by non-user-visible information
Adding POST data to every navigation action is a huge pain.
                        这篇关于在Django中将变量从Template转换为View的更有效的方法是什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！