<HTML>
<HEAD>
<TITLE>Re: Problem with nonces and HTTP GET</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi Andrew - <BR>
<BR>
POST responses require the OP to return HTTP 200 with a self-submitting form in the body. This causes the browser to display a blank white page as an interstitial before the RP’s return_to URL is loaded. Given that the RP’s return_to page will probably take a couple seconds to load (network latency, verifying the assertion, doing db lookups, etc) the blank white page really looks clunky.<BR>
<BR>
There are a couple hacks that can be done to make the POST form look more attractive, but that involves returning even more data in the response body.<BR>
<BR>
In contrast, the 302 Redirect/GET response does not display any blank interstitials between the time the response is sent to the browser and the the RP responds.<BR>
<BR>
There’s plenty of UX research that shows the effect of perceived latency where even a fraction of a second increase in latency results in a measurable decrease in user satisfaction. To encourage adoption, it’s very important that we match or exceed the UX standards that have already been set by the proprietary solutions.<BR>
<BR>
Thanks<BR>
Allen<BR>
<BR>
<BR>
On 1/28/10 6:02 AM, "Andrew Arnott" <<a href="andrewarnott@gmail.com">andrewarnott@gmail.com</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>On Wed, Jan 27, 2010 at 11:21 PM, Allen Tom <<a href="atom@yahoo-inc.com">atom@yahoo-inc.com</a>> wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>POST adds additional latency, and can cause strange warnings and a blank interstitial (the self submitting form). </SPAN></FONT><FONT SIZE="2"><FONT FACE="Arial"><SPAN STYLE='font-size:10pt'> <BR>
</SPAN></FONT></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
I agree with all your points, Allen. But can you explain why POST adds additional latency? It seems like just a word change over the wire. A browser and server shouldn't (it seems to me) take any longer to process it, except that it disables caching to some extent, but in this case that's desired.<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>