> Am 27.08.2015 um 10:22 schrieb jean-frederic clere <[email protected]>: > > On 08/24/2015 10:06 AM, Stefan Eissing wrote: >> Ni Norm, >> >> yes, I removed it last week > > If I want on VirtualHost with h2 support and another one without how should I > do that? (that is for demo purpose) > > Cheers > > Jean-Frederic
The default for "Protocols" is: everything. My thinking: when a Server loads mod_h2, it wants it enabled. 1st way (just do it): ------------------------------------------ <vhost *:443> ServerName with.example.org </vhost> <vhost *:443> ServerName without.example.org Protocols http/1.1 </vhost> 1st way (explicit h2, excluding any other in future enabled protocol): ------------------------------------------ Protocols h2 http/1.1 <vhost *:443> ServerName with.example.org </vhost> <vhost *:443> ServerName without.example.org Protocols http/1.1 </vhost> 2nd way (the careful way): ------------------------------------------ Protocols http/1.1 <vhost *:443> ServerName with.example.org Protocols h2 http/1.1 </vhost> <vhost *:443> ServerName without.example.org </vhost> <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
