Prerendering does not have any distinguishing HTTP headers

Adam Malcontenti-Wilson

unread,

Jun 15, 2011, 11:13:12 AM6/15/11

to Prerender

Hi. I previously submitted a bug report ( crbug.com/86175 ) because I
didn't see that this group even existed.
Basically, prerendering requests don't have any distinguishing HTTP
headers, so it is impossible to detect and handle them server-side.
See the bug report for more explanation/example of why this is needed.

PhistucK

unread,

Jun 15, 2011, 1:06:27 PM6/15/11

to Adam Malcontenti-Wilson, Prerender

Do you not see this header (that pre-rendering test currently fails for me with Chrome 14.0.792.0 canary and with 13.0.782.20 dev-m), so I cannot test it)?

Purpose:

prefetch

☆PhistucK

Adam Malcontenti-Wilson

unread,

Jun 15, 2011, 2:39:42 PM6/15/11

to Prerender

Nope... nothing like that..

GET http://prerender-test.appspot.com/?prerender-id=1308163064810-0.29674235288985074
HTTP/1.1
Host: prerender-test.appspot.com
Connection: keep-alive
Referer: http://prerender-test.appspot.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1
(KHTML, like Gecko) Chrome/13.0.782.20 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-AU,en;q=0.8,en-GB;q=0.6,en-US;q=0.4
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

I was using Chrome 13.0.782.20 dev-m as well and was able to use the
test page, perhaps you need to use --prerender=enabled if it's not on
automatically.

On Jun 16, 3:06 am, PhistucK <phist...@gmail.com> wrote:
> Do you not see this header (that pre-rendering test currently fails for me
> with Chrome 14.0.792.0 canary and with 13.0.782.20 dev-m), so I cannot test
> it)?
> Purpose:
> prefetch

> ☆*PhistucK*

>
> On Wed, Jun 15, 2011 at 18:13, Adam Malcontenti-Wilson

> <adman....@gmail.com>wrote:

Dominic Hamon

unread,

Jun 15, 2011, 3:07:05 PM6/15/11

to Adam Malcontenti-Wilson, Prerender

On Wed, Jun 15, 2011 at 11:39 AM, Adam Malcontenti-Wilson <adman.com@gmail.com> wrote:

Nope... nothing like that..

GET http://prerender-test.appspot.com/?prerender-id=1308163064810-0.29674235288985074
HTTP/1.1
Host: prerender-test.appspot.com
Connection: keep-alive
Referer: http://prerender-test.appspot.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1
(KHTML, like Gecko) Chrome/13.0.782.20 Safari/535.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
*;q=0.8
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-AU,en;q=0.8,en-GB;q=0.6,en-US;q=0.4
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

I was using Chrome 13.0.782.20 dev-m as well and was able to use the
test page, perhaps you need to use --prerender=enabled if it's not on
automatically.

If you are seeing that prerendering is disabled when navigating to prerender-test.appspot.com, it's possible that you have been put into a control group in which prerendering is disabled by default. You can use the --prerender=enabled command-line flag to force it to be enabled.

Adam Malcontenti-Wilson

unread,

Jun 15, 2011, 3:46:00 PM6/15/11

to Dominic Hamon, Prerender

That output *was* from chrome running with --prerender=enable .

--
Adam Malcontenti-Wilson

Alex Komoroske

unread,

Jun 15, 2011, 4:57:36 PM6/15/11

to Adam Malcontenti-Wilson, Dominic Hamon, Prerender

Thanks for reaching out, Adam!

As I said in another thread, prerendering in Chrome is a new technology and as it matures feedback like this will be really helpful.

We'll keep that issue you filed updated (we put the correct labels on it, as well).

--Alex

Reply all

Reply to author

Forward