W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2010

[whatwg] element "img" with HTTP POST method (2)

From: Philipp Serafin <phil127@gmail.com>
Date: Thu, 09 Dec 2010 21:09:46 +0100
Message-ID: <4D01378A.6060800@gmail.com>
... on second thought, maybe  it would be an even better idea to just
define a new "submit" like input type that would submit the form as soon
as it's fully loaded and display the POST result as an image. This would
work better with the form metaphor and would present less security
risks, since only very few sites allow <form> or <input> elements in
user content.

Martin Janecke's example would then look like this:

<form method="post" action="http://www.forkosh.dreamhost.com/mathtex.cgi">
 <input type="hidden" name="latexdata" value="\begin{align} (... latex
...) \end{align}">
 <input type="post-image">

On 09.12.2010 20:41, Philipp Serafin wrote:
> On 09.12.2010 20:04, Ashley Sheridan wrote:
>> It makes sense in the case of a link like that, as it is changing
>> some state on the server, which is what POST data was intended to do.
>> If images are called with POST data, then that would prevent them
>> being cached, which can be done with GET as GET isn't meant to change
>> any state on the server, meaning potentially a lot more traffic to
>> save some log files from getting a bit big.
>> Thanks,
>> Ash
>> http://www.ashleysheridan.co.uk
Received on Thursday, 9 December 2010 12:09:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:02 UTC