Make WordPress Core

Opened 7 years ago

Closed 7 years ago

Last modified 7 months ago

#8269 closed feature request (invalid)

Support SSL with different domain names, and sharing SSL domain

Reported by: reppep Owned by: ryan
Milestone: Priority: high
Severity: major Version: 2.6.1
Component: Security Keywords: SSL needs-patch
Focuses: Cc:


Admin-SSL supports different prefices for secure and insecure access.

For instance, all logged-in / wp-admin access for <http://www.extrapepperoni.com/> is under <https://secure.reppep.com/ep/>, and all admin access for <http://www.mscrochety.com/> is under <https://secure.reppep.com/mscrochety/>.

First, WordPress' built-in SSL features should support this configuration. It's not clear, but appears that the HTTP & HTTPS URLs must be the same, except the scheme, which prevents clean SSL for sites without an IP for each blog.

Second, WordPress MU should support this as well. Admin-SSL's WordPress MU support lacks the "Shared SSL" capability available for non-MU WordPress.

Change History (7)

#1 @jacobsantos
7 years ago

  • Keywords needs-patch added; Security MU removed
  • Type changed from enhancement to feature request

This would require a change to the way that SITE_URL and HOME_URL works, and would probably need a new SECURE_URL option in the database, as well as constant, and ability to set the location in the administration panel.

#2 @blenjee
7 years ago

I'm happy to offer assistance for the coding of this feature - my experience re-writing Admin SSL tells me it is not easy getting WordPress to work like this.



7 years ago

  • Milestone changed from 2.8 to Future Release

#4 @Denis-de-Bernardy
7 years ago

  • Milestone changed from Future Release to 2.8
  • Resolution set to fixed
  • Status changed from new to closed

this can be done using a plugin: site_url(), content_url(), login_url() and admin_url() all have filters in trunk, allowing you to override where they go.

#5 @Viper007Bond
7 years ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

#6 @Viper007Bond
7 years ago

  • Resolution set to invalid
  • Status changed from reopened to closed

#7 @DrewAPicture
7 months ago

  • Milestone 2.8 deleted
Note: See TracTickets for help on using tickets.