To www or not www

Re:To www or not www by z3t4 on Saturday March 18, 2017 @03:53PM (#13903182)

Connection limits to CDN from naked domain might also be limited. Can anyone confirm ? Ex: if browser limit is 2 connections per host, bare + sub will only give 2 connections, while sub + sub will give 4 connections.

If you are using Websockets or AJAX the connection limit can become an issue.

Also some users always write www in front of the domain. Although some browsers will just redirect to Google. So if you check browser referer a lot will be from www.google.com?q=www.yourdomain.com

[ Parent | on HN ]

Re:To www or not www by bobfunk on Saturday March 18, 2017 @04:21PM (#13903313)

With HTTP2 support this is not longer really a problem, since HTTP2 multiplexes requests over 1 connection.

[ Parent | on HN ]

Re:To www or not www by jrochkind1 on Sunday March 19, 2017 @01:23AM (#13905390)

I think few web apps (aka software driven sites, not just static content) use http2 yet.

[ Parent | on HN ]

Re:To www or not www by aidos on Saturday March 18, 2017 @04:34PM (#13903384)

I believe the Chrome connections per host is now 6 (even under old school http). Not sure about the other browsers.

[ Parent | on HN ]

Re:To www or not www by Klathmon on Saturday March 18, 2017 @09:19PM (#13904557)

I believe most are 6 and have been for at least a few years.

[ Parent | on HN ]