Conditional Headers based on User Agent

answered
#1

So I wanted to implement http2 push. But there is some varying browser support at the moment which might result in performance degradation on a few browsers.

So I was hoping if I could target only specific browsers?

#2

Hey Aziz,

We don’t have server push enabled right now, so it’s a bit of a moot point. I’m working with our documentation team to remove the documentation about it since I don’t know how soon we’ll re-enable it. However, we also don’t have functionality at the headers or redirect level to target specific browsers at present.

I’ve added this thread to our feature-request-tracker, which brings two benefits:

  1. So folks are encouraged to do the same thing as you, and spell out their (related - we’ll start a new thread for other features) use case in detail. It’s often the case that we have a workaround, or that there is some other way to achieve their goal, plus that use case will inform our eventual feature development in case we do implement the feature.
  2. if you’ve indicated interest, we can follow up to let you know if we do ship the feature at some point in the future.
1 Like
#4

Oh :sweat: :sweat_smile:

Can you share why you had to disable it, @fool? Would love to learn from your experience.

Also can you add these points as part of the feature request (Maybe “Good to have” :sweat_smile: )

  • “Cache-aware Server Push” like H20 or mod_http2’s H2PushDiarySize directive.
  • Bandwidth use statistics. Percentage Usage by H2 Push. This might help users debug if they have implemented something wrong with H2 push or are abusing it.
  • Good defaults on which User Agents to push assets. (Maybe allow overriding)
1 Like