max

thanks for this, will look at network functions, better late than never =)

aloha, max

If you can understand below, there is some useful stuff in there for your need…
If you can’t understand below, then don’t use it!

`<IfModule mod_rewrite.c>
RewriteEngine On
Options All -Indexes
#BEGIN Remove ‘www.’ from all Requests
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [R=301,L]
#END Remove ‘www.’ from all Requests
#BEGIN Frontend Address Control for Network Subsites with Mapped .Com
RewriteCond %{REQUEST_URI} !^/?wp-(admin|content|includes|login) [NC]
RewriteCond %{HTTP_HOST} ([^.]+)-secure-1\.example\.tld$ [NC]
RewriteCond %{QUERY_STRING} !preview=true [NC]
RewriteRule ^ https://%1.com%{REQUEST_URI} [R=301,L]
#END Frontend Address Control for Network Subsites with Mapped .Com
#BEGIN Frontend Address Control for Network Subsites with Mapped .Net
RewriteCond %{REQUEST_URI} !^/?wp-(admin|content|includes|login) [NC]
RewriteCond %{HTTP_HOST} ([^.]+)-secure-2\.example\.tld$ [NC]
RewriteCond %{QUERY_STRING} !preview=true [NC]
RewriteRule ^ https://%1.net%{REQUEST_URI} [R=301,L]
#END Frontend Address Control for Network Subsites with Mapped .Net
</IfModule>

@halex I work w/ multisite alot… is your WPMS using subdomains or subdirectories?

any other special configs to know about?

I will test for this and repost if I have any issues ??

+1 for multisite support and awesome its on github now ??

Reputation takes years to build yet can be lost/eroded in a relative moment…

I also find myself doubting the update button with Yoast’s recent work, which is a condition I work hard to avoid – mostly by being very selective about who’s code I’m willing to run ??

Any others experiencing ongoing issues with 1.7.3.3 as @homerecords reports?

… since I just found this from the same user I quote above
https://github.com/etcio/wpmandrill-multisite/
I’m thinking that perhaps there has not been much change in Mandrill’s core support for WPMS… I’d appreciate any clarifications y’all are able to give.

Aloha ??

“No, it does not officially support multisite.”

??

“That said, you could probably get it to work by activating it separately on each site.”

Ever tried it? Any success Duke?

https://core.trac.www.ads-software.com/ticket/15928
https://github.com/wmark/CDN-Linker

some good leads there, good luck ??

I’d love to know if 5.1 has addressed your issue @gabernx

hope so ??

Hi @bhenselmann thanks for posting such a clear report of what was happening for you. Hope you get it sorted.

@nintechnet I’ve been reviewing your support threads, and y’all are really responsive & seem to be able to work to a resolution quickly & clearly ?? which is awesome!

Cheers, Max

+1

I am also interested in this answer… will poke around more.

fyi, i use subdomains & wpmudev’s domain mapping plugin

i am working on using https for backend & have used askapache.com as primary reference material. not easy, yet awesomely interesting ??

thanks askapache!

https://www.askapache.com/htaccess/crazy-advanced-mod_rewrite-tutorial.html
is the best, btw <3

I generally like to clean up after myself ??

Also, I wanted to make sure that were a few more threads out there to be found for the ‘Jetpack SSLv3 Handshake’ error… hopefully this can save someone else some time ??

Cheers, Max

Resolved.

see:
https://www.ads-software.com/support/topic/jetpack-connection-sslv3-handshake-failure-solution-check-1?replies=9#post-6174876

Resolved.

We have rebuilt the SSL cipher suite configuration on the server and this has resolved the issue with the connection through non-www URLs.

Yay! Thanks very much for your help Jeremy ??

Kind Regards, Max

For future searchers (though, hopefully none):

Heard back from Jeremy via email. (Thanks again!)

The problem seems related to your site’s SSL configuration: it does indeed only seems to support the RC4 cipher. WordPress.com is unable to connect to that site because Libcurl/curl dropped RC4 support by default in 7.35 if I’m not mistaken (the default list of supported ciphers is now ALL!EXPORT!EXPORT40!EXPORT56!aNULL!LOW!RC4). You can manually reproduce this problem on command line:

$ curl -I --ciphers 'ALL!EXPORT!EXPORT40!EXPORT56!aNULL!LOW!RC4' https://tivism.com/
curl: (35) error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert handshake failure

I will of course update with further info as available ??

Aloha, Max