HTTP/2 push issues with standalone Jetty deployment

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

HTTP/2 push issues with standalone Jetty deployment

jamie1
This post has NOT been accepted by the mailing list yet.
Hi,

I have setup a standalone Jetty server based on instructions from the documentation guide. The server seems to work great for HTTP/1.1 and HTTP/2 in general. However, with I try to enable HTTP/2 push, I do not seem to get it working. I have verified this using both chrome dev-tools and through chrome://net-internals. Both confirm that no objects are being pushed. Below is a copy of how my web.xml file looks and also attached is a screenshot from chrome dev-tools. I have also verified that the browser sends a referrer tag with all objects in the index file.



Could someone please help me fix this.
Thanks.
Jamie


------
<?xml version="1.0" encoding="UTF-8"?>
<web-app
    xmlns="http://xmlns.jcp.org/xml/ns/javaee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
    metadata-complete="true"
    version="3.1">
    <filter>
        <filter-name>PushFilter</filter-name>
        <filter-class>org.eclipse.jetty.servlets.PushCacheFilter</filter-class>
        <async-supported>true</async-supported>
        <init-param>
            <param-name>ports</param-name>
            <param-value>8443</param-value>
        </init-param>
         <init-param>
            <param-name>associatePeriod</param-name>
            <param-value>1500</param-value>
        </init-param>
        <init-param>
            <param-name>maxAssociations</param-name>
            <param-value>128</param-value>
        </init-param>
    </filter>
    <filter-mapping>
        <filter-name>PushFilter</filter-name>
        <url-pattern>*</url-pattern>
    </filter-mapping>

</web-app>
------