Meh - just wanted to show it. Anyway I just expect that the second response is from out of the cache instead the third. The second response was 200 OK but without response body.
kind regards Tobias > Am 06.09.2017 um 10:10 schrieb Martin Grigorov <[email protected]>: > > Hi Tobias, > > There are no attachments. > The mailing list strips them. > I'm not sure how some people attach files sometimes :-) > > Martin Grigorov > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Wed, Sep 6, 2017 at 10:01 AM, Tobias Soloschenko < > [email protected]> wrote: > >> Hi everyone, >> >> as usual I am just playing around a bit with HTTP/2 Push support and just >> wanted to ensure that the experimental push support of Apache Wicket is >> working like expected. :-) >> >> I basically followed the instructions on: >> https://ci.apache.org/projects/wicket/guide/8.x/ >> single.html#_wicket_http_2_support_experimental >> >> and setup my tomcat with HTTP/2 like described here: >> https://stackoverflow.com/a/45437449 >> >> I just get confused by Firebug a bit. I attached three screenshots. The >> first one is of the first request the seconds one of the second request and >> the third one of the third request. >> >> As you can see in the first one Firebug mentions that https SPDY is used >> which means that the resource has been pushed. (Which is ok) >> >> The second one I don't understand because it says 200 OK, but with no >> Response Body. I just expected the second one to be like the third in which >> the resource is received from out of the cache. >> >> Anyone know why this second step happens? >> >> kind regards and thanks in advance >> >> Tobias >> >> P.S.: I used FireFox, because Chrome doesn't cache resource of https >> connections that are not secure. >>
