Thanks to Eric and Stefan for replying.
On 9/16/15 11:51 AM, "Stefan Eissing" wrote:
>SPDY has been superceeded by HTTP/2 as a protocol. Some browsers still
>support SPDY, however it will int the mid-term go away.
>
>All major browsers nowadays support HTTP/2. That should make it a safer
>invest
SPDY has been superceeded by HTTP/2 as a protocol. Some browsers still support
SPDY, however it will int the mid-term go away.
All major browsers nowadays support HTTP/2. That should make it a safer
investment.
Apache httpd will support HTTP/2 in one of the next 2.4.x releases - hopefully
the
On Wed, Sep 16, 2015 at 11:35 AM, Rose, John B wrote:
> Is SPDY something that the typical Apache 2.2 or 2.4 installation should be
> utilizing as of September 2015?
>
No, if anything look into mod_h2 if you have a requirement in this area
> Are there any reasons to NOT use SPDY?
Yes, the proto
We have some Apache 2.2 and 2.4 web servers
We are determining if we should pursue setting up SPDY on our Apache 2.2 and
2.4 web servers.
At one time I thought SPDY only worked over https with limited browsers, but
additional reading looks like that is not true.
I see that Google has dropped s
I have a Joomla 3 install running on an Apple Intel XServe running Mac OSX
10.6. I built the site in a directory in the web root (virtual_site) and when
the site was ready I pointed a name-based virtual host to that directory. The
site MOSTLY comes up when you go to the host name, but there are
Yes, looks like you're right. It seems odd that we have some paths that
assign r->headers_out and some that don't.
In any case, here is the updated patch. It may be worth opening this as a
bug report so we can keep track of it easier.
On Wed, Sep 16, 2015 at 3:47 AM, Yann Ylavic wrote:
> Hi E
Hi Ed,
On Tue, Sep 15, 2015 at 10:10 PM, Edward Lu wrote:
> This looks like a bug. I believe I've tracked down the cause to a single
> errant line in the cache module; can you apply the attached patch to 2.4.x
> and see if it fixes the problem?
I think the patch would also need this hunk:
Index
The redirect just permanently redirects everything to use https.
IMO you should fix this part by excluding the subset you want.
I tried adding another VirtualHost for port 80, with a DocumentRoot
pointed at my "freely-available" subdirectory.
Not sure why you need another VirtualHost, but in an
