DevOps:Doc/FlexForm/2.0/input/secure - Revision history

Fd4138e7-8b46-4c8f-99bf-d4b738ebc295: Text replacement - "|Subject version=2.0,2.1" to "|Subject version=2.0,2.1,2.5"

2025-08-21T09:07:29Z

Text replacement - "|Subject version=2.0,2.1" to "|Subject version=2.0,2.1,2.5"

ws-class-props
← Older revision		Revision as of 11:07, 21 August 2025
Line 1:		Line 1:
	{{Csp class properties		{{Csp class properties
	\|Subject version=2.0,2.1		\|Subject version=2.0,2.1,2.5
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
	\|Doc parent=DevOps:Doc/FlexForm/1.0/input		\|Doc parent=DevOps:Doc/FlexForm/1.0/input

Maintenance script: Imported by PageSync

2025-07-15T08:34:20Z

Imported by PageSync

ws-class-props
← Older revision		Revision as of 10:34, 15 July 2025
Line 1:		Line 1:
	{{~~Doc~~ properties		{{Csp class properties
	\|Subject version=2.0,2.1		\|Subject version=2.0,2.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm

Charlot: User:Charlot

2023-03-31T20:09:50Z

User:Charlot

ws-class-props
← Older revision		Revision as of 22:09, 31 March 2023
Line 1:		Line 1:
	{{Doc properties		{{Doc properties
	\|Subject version=2.0		\|Subject version=2.0,2.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
	\|Doc parent=DevOps:Doc/FlexForm/1.0/input		\|Doc parent=DevOps:Doc/FlexForm/1.0/input

Charlot at 09:13, 3 January 2023

2023-01-03T09:13:25Z

← Older revision		Revision as of 11:13, 3 January 2023
Line 2:		Line 2:
	secure		secure
	===Type===		===Type===
	~~_input~~		input
	===Synopsis===		===Synopsis===
	How to render a hidden input field that is secure		How to render a hidden input field that is secure

Charlot at 09:13, 3 January 2023

2023-01-03T09:13:09Z

← Older revision		Revision as of 11:13, 3 January 2023
Line 6:		Line 6:
	How to render a hidden input field that is secure		How to render a hidden input field that is secure
	===Description===		===Description===
	~~_input~~ elements of type secure are similar to type hidden. The difference is that a secure field is not readable by a user and a form will fail if it gets altered using Browsers developer tools		input elements of type secure are similar to type hidden. The difference is that a secure field is not readable by a user and a form will fail if it gets altered using Browsers developer tools
	===Parameters===		===Parameters===
	type="secure"		type="secure"
Line 13:		Line 13:
	===Example===		===Example===
	<syntaxhighlight lang="html">		<syntaxhighlight lang="html">
	<~~_input~~ type="secure" name="token" value="123231321" />		<input type="secure" name="token" value="123231321" />
	</syntaxhighlight>		</syntaxhighlight>
	This will render something similar to		This will render something similar to

Charlot: User:Charlot

2023-01-03T09:12:26Z

User:Charlot

ws-class-props
← Older revision		Revision as of 11:12, 3 January 2023
Line 5:		Line 5:
	\|Doc sort order=110		\|Doc sort order=110
	\|Doc target group=User		\|Doc target group=User
			\|Doc synopsis=How to render a hidden input field that is secure
	}}		}}

Charlot: User:Charlot

2023-01-03T09:12:10Z

User:Charlot

New page

===Name===
secure
===Type===
_input
===Synopsis===
How to render a hidden input field that is secure
===Description===
_input elements of type secure are similar to type hidden. The difference is that a secure field is not readable by a user and a form will fail if it gets altered using Browsers developer tools
===Parameters===
type="secure"

All other valid parameters for an input field are valid
===Example===
<syntaxhighlight lang="html">
<_input type="secure" name="token" value="123231321" />
</syntaxhighlight>
This will render something similar to
<syntaxhighlight lang="html">
<input name="2425fb14579653aef53179a2849e4593ES5rgMk=" value="7cade404c7d02c02a3087e4fd6954caby0QljHbAPys0" type="hidden">
</syntaxhighlight>
===Note===
When using action="get" a secure field will not be returned in the url
===Links===