Hot!Specific web request failed when called via HTTP2

Author
mheronline
New Member
  • Total Posts : 1
  • Scores: 0
  • Reward points: 0
  • Joined: 2018/11/21 10:57:49
  • Status: offline
2018/11/21 14:51:11 (permalink)
0

Specific web request failed when called via HTTP2



We have a single http2 request failing when called with OPTIONS method. The device is running as Reverse Proxy, we don’t have any protection policies applied. In the server policy and server pool we have HTTP2 feature enabled. The backend is nginx 1.14 running on docker, which in it’s turn proxies connections to another container running java web API. We fully support HTTP2 all the way up to the web service. The same call works when called directly to nginx with http2. It works even when goes through WAF but only in case we called it via http/1.x specifically. Apart from this specific call we have a lot of other similar and they all work fine both with http/1.x or http2. Any idea on what could be the issue is much appreciated. 
 
Here is the request failing:  https://example.domain.co...r.myWorkspace,nav.bar.
applications,nav.bar.households,nav.bar.cases,nav.bar.pageManagement,nav.bar.section.title,nav.bar.um,nav.bar.um.organizations,
nav.bar.um.users,nav.bar.um.roles,nav.bar.um.groups,nav.bar.configurations,nav.bar.notification.templates,nav.bar.smpp.config.ui,nav.
bar.smtp.config.ui,nav.bar.job.manager.service.ui,nav.bar.programme.management,nav.bar.categories,nav.bar.monitoring,nav.bar.policies,nav.bar.audit,
#1

1 Reply Related Threads

    benjamin_harrison
    New Member
    • Total Posts : 2
    • Scores: 0
    • Reward points: 0
    • Joined: 2019/05/06 05:01:00
    • Status: offline
    Re: Specific web request failed when called via HTTP2 2019/05/07 23:08:49 (permalink)
    0
    rather than using http2 use https, http2 is not more used in web protocols, all the aspects you have written here are good example of navbar.
    #2
    Jump to:
    © 2019 APG vNext Commercial Version 5.5