What is the reasoning for including the http(s) protocol?

  • jimbotechsys

    (@jimbotechsys)


    9 years, 10 months ago

    What on Earth is the reasoning behind including the protocol (HTTP or HTTPS) with any and all link references in WP? Does anyone actually know?

    How is it possible that this requirement is more important than all of the problems and potential errors that occur when changing every single link on a site as well as in theme configurations and who knows where else?

    If I need to run a site as BOTH secure and non-secure simultaneously with the same EXACT content, am I to understand it is NOT possible without duplicating the site for the OTHER protocol?

    Why is this ridiculous mandate still required? Isn’t WP supposed to make it easier, not more difficult?

Viewing 1 replies (of 1 total)
  • Moderator James Huff

    (@macmanx)

    9 years, 10 months ago

    It’s currently the way it is because it’s the way it is. WordPress is built by volunteers, and if I had to guess, WordPress still requires a choice of protocol because no one has volunteered their time to make it otherwise. If you’d like to help, I recommend starting by filing this as a bug and contributing a patch if you can: https://make.ww.wp.xz.cn/core/handbook/testing/reporting-bugs/

    For now, I recommend sticking with just HTTPS. The protocol has advanced significantly in the past year. Most browsers cache it, it’s a requirement for security obviously, and some server configurations actually serve it faster than HTTP.

Viewing 1 replies (of 1 total)

The topic ‘What is the reasoning for including the http(s) protocol?’ is closed to new replies.