HTTP/2 allows a server to push resources to the client rather than waiting for the client to parse the main HTML document
and then request further resources one by one. Typically, HTTP/2 servers push files like style sheets and images to the client.
Clients usually require these resources anyway to render a page.
You can enable and disable server push in the Profile Settings: Click
.
- In
TrueLog Explorer pushed resources are represented by nodes with
(server push) appended. For these nodes the tabs
Out Header and
Out Body are disabled. If the resource is required in subsequent pages, cache hits are generated as usual.
- If you request a page several times, the server will attempt to push the same resources several times. However,
Silk Performer stores the pushed resources only once and notifies the server that additional pushes are not required. If the server has
already started pushing resources before it receives the notification, the related traffic will not be measured by
Silk Performer.
- If
Silk Performer detects a resource that has been pushed by the server but is actually not required during a
WebPage* function call, a warning displays in the virtual user output and in
TrueLog Explorer. Such a warning indicates a server misconfiguration, because the server pushes resources that are not required. This again
produces unnecessary network traffic.
In some cases, the
Silk Performer push support might differ from the behavior of real browsers. Browsers have different push cache implementations, because
there is no official push cache specification.