►
From YouTube: WebPerfWG TPAC meetings 2022 09 12 - No-Vary Query
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
A
All
right
so
yeah,
so
this
is.
B
B
B
Jeremy
and
I
put
this
together,
based
on
looking
at
this
from
the
perspective
of
the
preload
caches
for
document
pre-render
and
prefetch,
but
we
think
it
could
be
pretty
widely
applicable
to
a
lot
of
different
factors
on
the
webcock
market
and
we
did
the
analysis
on
where
this
could
go.
So
this
includes
these
be
cash,
but
also
things
like
service
worker
trash
API
share
worker
cash.
A
Hits
fewer
cash
so
yeah.
So
let's
go
down.
B
The
syntax,
so
the
first
thing
that
you
can
do
with
this
header
is,
you
can
say
it
doesn't
matter
what
the
order
of
the
green
frames
are.
Please
treat
all
different
orders
the
same
when
creating
the
catch
key
when
doing
a
lookup.
Another
thing
you
can
do
is
say:
okay,
please
ignore
these
specific
query
params
when
you're
constructing
the
Clash
key
to
do
a
lookup
like
that.
B
We
they
do
not
matter,
and
then
you
can
also
just
flip
that
and
say:
okay,
excuse,
ignore
everything,
except
this
one
cache
key
which,
over
this
one
create
brand,
which
is
the
actually
important
one.
So
some
of
you,
this
may
seem
like
clear
why
this
would
be
useful,
but.
A
Just
to
go
through
some
of
the
use
cases
we
found
in
particular
one
is
just
the
inconsistent.
B
Refers
right
so
there
would
be
external
sites
or
Legacy
parts
of
your
site
you'll.
Have
it
completely
created
an
economical
way
of
referring
to
a
URL
on
your
page?
They
might
append
random
things.
Random
group
grams,
I'll
assume
they
do
nothing.
They
might
use
different
order.
That
sort
of
thing
so
it'd
be
really
nice.
If
you
could
say
like
actually
just
please
give
me
a
cash
paid,
even
if
the
referrer
isn't
perfect.
B
Are
important
customizations
and
you
really
need
them
to
cause
different
responses
and
be
cached
differently,
but
in
many
cases
they're
not
right
like
if
you
have
server
side,
debug
login
was
turned
out
in
the
first
time.
It's
really
fine.
It's
like
when
you're
going
to
look
it
up.
We
promise
you,
don't
you
don't
need
to
recompute
it
without
server
side?
That
sort
of
thing
you
know
ideally
distorted
metadata.
B
Since
it's
really
not
part
of
like
the
resource
identity,
we
can
go
in
the
URL
metadata
like
a
good
place
to
put
headers
or
a
good
place
to
put
metadata,
but
there's
a
lot
of
places
in
the
web
platform
that
don't
let
you
just
specify
auditory,
headers,
Iran's
links
being
obvious.
A
B
One
is
when
you
have
data
that
is,
or
can
be
processed
by
client-side
scripts
right
so
like
something
saying
analytics
where
users
should
be
redirected.
Some
detail
definitely
on
the
page,
something
like
that.
So
in
theory,
because
this
is
for
client-side
processing,
you
could
possibly
have
a
fragments.
We've
seen
him
practice
a
lot
of
sites,
usually
very
just
because
that's
what
they're
used
to
or
perhaps
even
because.
B
Using
server-side
rhetoric
most
of
the
times,
this
gets
a
little
more
interesting
when
you
have
preloading,
you
know
pre-fetching
and
pre-rendering,
where
they
might
be
interested
in
getting
a
pre-render
and
then
doing
this
stuff
client-side
as
long
as
they
can
get
the
benefits
of
three
rendering,
like
oh
yeah.
Also,
it's
I'm
doing
that.
Maybe
someone
basically
pre-rendering
the
changes.
The
pharmacists,
a
little
note
on
analytics
and
probably
navigational
tracking
and
talk
about
that
more
as
you
want.
B
Yeah
and
then
a
similar
example,
kind
of
in
a
little
more
detail
is
specific
to
the
the
pre-rendering
or
pre-frection
case.
So
here's
an
example
using
the
speculation
rules,
API
that
we've
been
working
on
so
here
I
have
a
like
a
kind
of
like
a
mock-up
of
the
news
site
if
I
was
like
a
hero
image
and
it
has
a
headline-
and
it's
like
okay-
well,
let's,
let's
tell
the
the
article
where
we
reached
it.
Do
we
reach
that
via
the
zero
image
or
via
the
headline?
B
Well,
you
don't
really
want
to
spin
on
two
separate
pre-renderers
for
these
two
like
separate
resources.
That
would
just
be
a
waste,
but
you
also
do
want
to
preserve
that
information
when
the
user
does
click
one
of
these.
So
what
we've
said
is
that
you
can
say:
okay,
please
pre-render
like
the
base
URL
and
then
the
browser
will
go
off
and
reimburse
with
no
query
Brands
and
then,
once
you
go,
click
on
one
of
these,
the
browser
will
kind
of
Doom
the
appropriate
stuff
behind
the
scenes
they.
B
Actually,
this
is
the
the
link,
the
user.
Actually,
please
update
the
pre-render
and
activators.
So
you
didn't
have
to
peer
render
twice,
because
and
and
this
is
only
doable
if
you
signal
this
destination
page
signals.
A
Okay,
I'm;
okay,
to
ignore
the
group
frames
yeah
like
key
on
its
value.
B
So
yeah
it's
exactly,
it
would
say.
No
very
query
right,
don't
vary
near
the
view,
yeah
all
right,
detailed
design,
it's
a
it's
a
structured
header!
Everything
goes
with
the
structured
header
these
days
right,
so
integration
with
all
the
different
caches.
This
is
also
interesting.
So
there's
a
specific
sentence
in
base
PRC,
which
is
like
how
you
construct
accounts
key.
B
This
would
modify
that.
There's
some
details
about
exactly
what
we
modify
in
terms
of
requests
to
our
inverse
response.
Uri.
Let
me
get
into
that
a
little
bit
later,
but
I'll.
Just
let's
go
over
to
all
the
questions
that
I
want
running.
So
the
pre-loading
captions
are
a
big
one.
These
are
keyed
By,
Request
URL,
and
we
have
one
for
prefights
and
one
for
pre-rendering,
and
this
is
this
one
applying
to
those
as
well
when
you're
doing
captions
up
there.
B
The
service
worker
cache
API
already
has
like
the
very
header.
This
would
just
be
kind
of
very
similarly
there's
some
details
on
like
the
API
and
how
you
can
customize
it
and
then
there's
a
bunch
of
other
URL
key
crashes
on
the
web
top
form.
These
are
ones
that
we
talked
about
my
head,
it
might
be
exhaustive,
but
I
wouldn't
really
want
to
bet
on
it,
but
we
just
generally
think
this.
This
is
not
something
we
necessarily
you
want
to
update
right.
B
Maybe
one
of
the
the
bigger
details
is
like
to
emphasize
that
we're
not
changing
the
response
that
it's
getting
so
there's
the
URL
of
the
response
that
is
getting
sent
back.
So
when
you
get
one
of
these
things
from
the
cache,
let's
say
it
was
via
hero
image
when
you
catch
it
and
now
you're
doing
a
request
where
the
Via
equals
headline.
B
A
And
displayed
it's
the
URL
where
the
user
was
headed,
honor,
none
of
that
changes,
yeah,
that
is
my
email
requester
previously.
B
They
were
notified.
This
is
more
complicated
for
pre-rendering,
where
there's
like
an
entire
document
construction
life
cycle
before
we
actually
pull
out
or
before
we
actually
know
the
final
URL.
So
our
solution
is
that
we
constructed
and
everything
via
the
original.
A
And
then
on
activation
here
on
activation,
we
at
the
same
time
we
fire
the
pre-rendering.
B
A
B
It's
just
basically
like
it's
the
request,
your
own
versus
responsible
thing,
so
you
have
to
and
like
what.
If
some
redirects
have
the
header.
A
And
some
don't
the
redirects
come
from.
Yes,.
B
I
think
they
can
come
from
cash,
yeah
yeah,
so
things
like
that.
So
I've
worked
out
some
examples
of
like
okay.
What
if
this
rewrites
how's
the
cutter-
and
you
can
end
up
in
some
weird
situations
where
it's
like,
if,
if
you've
captured
or
redirect
with
one
of
these
headers
user,
might
see
something.
A
That
they
didn't
didn't
quite
expect.
So
in
that
case
you
should
either.
A
Yeah,
as
for
the
other
for
the
the
other
caches,
if
we
were
to
do
them,
including
the
pre-rendered
questions,
if
you
want
to
do
request
crash,
this
would
only
apply
to
the
URL
that
gives
us
back
the
header
right.
So
if
there
is
a
redirect,
you
basically
want
to
put.
A
Get
into
that
discussion
section
as
I
said,
we'll
rename
it.
A
A
Or
case
and
sensitivity,
or
so
on,
improving
this
impacts.
B
For
that
another
thing:
that's
really
interesting,
but
not
what
we're
focused
on
is
maybe
allowing
the
same
type
of
power
for
path
instead
of
just
query
strings
from
a
security
perspective.
This
is
kind
of
okay,
because
the
security
boundary
is
the
origin,
and
this
can
be
really
useful
for
client-side,
rendering
single
page
apps,
where
they
just
want
to
give
the
same
response
from
the
Cache,
no
matter
what,
but
it's
it's
more
delicate.
B
It's
you
notice
that
service
workers
did
not
give
everybody
the
ability
to
rewrite
paths
like
they
have
some
path
restrictions
so
there's
at
least
a
lot
of
security
sensitivity
there
and
definitely
the
syntax
is
very
different.
Queries.
Korean
frames
are
like
an
unordered,
multi-mount
or
mostly
unordered,
multi-map,
but
path.
A
Was
like
a
slash,
separated
segment
of
strings,
so
you
definitely
don't
want
to
try
and
example,
into
the
same
header.
So
that
was
why
maybe
we
split
off
there's
a
use
case
to
do
with
details
of.
B
Preloading
on
how
maybe
you
want
to
let
the
refer
indicate
what
it
thinks,
but
no
very
query
will
be
you
can't
really
let
the
referred
feel
coordinated
about
this,
at
least
in
the
cross-orging
case,
but
there
are
some
cases
which
it
could
save
some
preloading.
A
What's
up
sorry,
I
just
had
a
quick,
no
just
like
yeah.
Let's
get
questions
together.
B
All
right
all
right,
almost
done
last
feature.
Extension
is
a
meta
version.
As
always,
HP
headers
are
hard
to
deploy.
Maybe
we
could
get
what
I
was
doing
this
in
the
meta
it
would
be
kind
of
icky,
especially
like
this
would
be
the
first
time
the
HP
couch
looks
into
the
internet.
B
B
You
know
this
is
opt-in,
so
a
lot
of
the
kind
of
like
attack
type
scenarios,
fireworks
mitigated
because
you
have
to
be
doing
this
to
yourself
for
privacy.
You
know
you
might
think
this
is
related
to
kind
of
the
the
link,
decoration
and
navigational
tracking
space,
but
we
think
it's
pretty
orthogonal,
no
matter
we
you
know
that's.
B
This
is
about
saying:
please
treat
True
Values
the
same
like
like
don't
pay
attention
to
this
great
brand,
whereas
doing
navigational
tracking
would
be
a
great
Branch
relies
on
like
treating
them
very
differently
and
in
general,
like
looking
at
all
the
mitigations
that
are
being
done,
and
people
have
thought
about
doing.
A
None
of
them
would
really
be
impacted
by
this
world.
So
pretty
sure,
there's
there's
nothing
there.