[wp-hackers] Two new, long-overdue plugins to make your wordpress life a little easier...
Marcus Pope
Marcus.Pope at springbox.com
Sat Oct 29 20:33:10 UTC 2011
Mike, app urls do not have to change or be post processed. With root-relative urls you inherently do not specify http or https on links returned to the browser and the browser will maintain that ssl connection for you, guaranteed. In the event that someone navigates directly to an http url when they should have gone to https wordpress already does a redirect to the proper scheme.
They do not apply to back end functions only. Install my plugin and browse a front end page. You will see just how often they are called with a simple debug statement to your error log. get_site_url and others in that patch are universally executed functions (front and back.)
Hope that information helps you find what I'm referring to.
Marcus Pope
Senior Developer
Springbox
512-968-3585
On Oct 29, 2011, at 10:10 AM, "Mike Little" <wordpress at zed1.com> wrote:
> On Sat, Oct 29, 2011 at 02:59, Marcus Pope <Marcus.Pope at springbox.com>wrote:
>
>> Mike Little, I know I said I'd drop the topic on this list, but I didn't
>> want to ignore your requests for information.
>>
>> You can look at the patch I referenced, you'll see line numbers and file
>> names, there are a lot of references so it's just easier to look here...
>> http://core.trac.wordpress.org/attachment/ticket/19037/ssl.patch
>>
>> Everything that passes through things like get_site_url in
>> link-template.php, self_link in feed.php, class-wp-xmlrpc-server.php etc
>> gets processed, and there are a bunch of links that go through those low
>> level functions.
>>
>>
> But there are not *content* urls. These are the app urls to take you to the
> edit page or the plugins page . They *have* to change from one site to
> another, and because WordPress allows you to run the back end half of your
> installation on https separate from the front end half, then yes, there
> *has* to be a check and a possible replace http for htps. But, as I say,
> this is the back end admin functions and those are accessed very
> infrequently compared to the front end *content*
>
> This example does not support your case.
>
>
> Mike
> --
> Mike Little
> http://zed1.com/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
More information about the wp-hackers
mailing list