I would like to install wordpress multisite on a live server and have one of the sub-domains be https.  The main site is not https and neither are the other sub-domains. Is that possible?  Thanks!
124288
I need a single Wordpress installation to be available from both the main domain (www.example.com) via HTTP and a subdomain (secure.example.com) via HTTPS.  Of course i can just map the subdomain to the Wordpress folder in Nginx config. But will Wordpress be aware that it is called via HTTPS and change all links on the pages to HTTPS ?  Also, how i can i force certain pages to be automatically redirected to their HTTPS equivalent permalink (and then back again to HTTP) ?
7138
With the advent of the WordPress Answers Stack Exchange site, there's undoubtedly going to be overlap.  But I just want to get some advice:  I'm a developer and I kinda hate WordPress, but have to use it occasionally. My WordPress questions are usually development ones (when I have them), and most often related to 'how WordPress handles things', which are pretty obvious in straight programming terms.  But with the WordPress layer of abstraction, they become problematic.  I find that most developers that have gone near WordPress are usually also PHP/JS/CSS/MYSQL guys who dabble with WordPress and, as a result, hangout more on SO. And theres a die hard bunch who are heavy into the WP.SE site, but generally the WP site is for people trying to muddle through the day to day operation of using WordPress and its many themes/plugin etc.    As a result, if I were to ask something pretty in-depth about writing / integrating new &amp; strange features or something, I'm talking to a much smaller group of devs than I would be on SO.  So, enough of the ramble, my question:  Should I be posting heavy development questions relating to WordPress on the WP.SE site or to SO? Can I post to both, or is cross posting frowned upon in these cases still?
66283
My code doesn't work with second level tld's like domain.co.uk Here is my conf:   # add www.   if ($host ~ ^(?!www)) {    rewrite ^/(.*)$ http://www.$host/$1 permanent;   }    # remove subdomain   if ($host ~ &quot;^www\.(.*)\.(.*\.([a-z]{2,4}|[a-z]{2}\.[a-z]{2}))&quot;) {    set $host_without_sub $2;    rewrite ^/(.*)$ http://www.$host_without_sub/$1 permanent;   }
81770
I want to create a multisite with Drupal 7: Every site works separately but users, and nodes must be shared among the sites.   How do I achieve it?
81759
Right now my site runs on http://www.example.com but I need to run that without www also i.e example.com  Can some body tell me here that how can i do that?
64077
Following the recent Google announcements about  we have a number of clients asking about this. Is it safe to just 301 redirect all pages to their SSL equivalent, for example in a common PHP include file:  if($_SERVER['HTTPS']!="on"){     $redirect= "https://".$_SERVER['HTTP_HOST'].$_SERVER['REQUEST_URI'];     header("Location:$redirect",true,301);     exit(); }   Obviously I'm aware this is also possible within a .htaccess file but that cannot be modified in our case.  Obviously all internal links would be switched to https:// links but obviously we need to sort out incoming links from Google and elsewhere.   Is this a sound approach? Are there any other gotchas to be aware of?
39181
Has anyone successfully embedded their  on a WordPress.com-hosted blog?  The free hosted version of  (not )  from all posts before publishing. So they to strip out just about anything I can add to embed my Stack Overflow flair.  Note: I'll be switching to a paid, hosted site in the future (fixing the problem), but I'm looking for a quick, short-term solution.
112755
I have some Ubuntu 16.04 server running and set up one vhost in apache2 which uses (or should use) ssl.  &lt;IfModule mod_ssl.c&gt;         &lt;VirtualHost *:443&gt;          ServerAdmin myemail@mailhoster.xx         ServerName my.domain.name.de         DocumentRoot /var/www/mysslsite          &lt;Directory /var/www/mysslsite&gt;                 Options FollowSymLinks MultiViews                 AllowOverride All                 Order allow,deny                 allow from all         &lt;/Directory&gt;          ErrorLog ${APACHE_LOG_DIR}/mysite.ssl.error.log         CustomLog ${APACHE_LOG_DIR}/mysite.ssl.access.log combined          &lt;/VirtualHost&gt; &lt;/IfModule&gt;   I did NOT enable the standard sites-available/default-ssl.conf.  I am able now to browse to  and it is asking in firefox to add some exception which is totally normal if i did not buy any certificate.  But I was wondering where it is set up that it should use the certificates in /etc/apache2/ssl/ directory. I can not find any config where it is told to use that. I all the time was thinking that it will use something from /etc/ssl folder.   Or did I maybe not activate SSL correctly?
91575
I'm trying to get apache to redirect from http to https, however I want them both on the same port (20100, but I doubt that will matter). Basically what's going on  except I'm not doing this for webmin. Currently I have it configured to serve HTTPS, and when I access with HTTP I get:  Your browser sent a request that this server could not understand. Reason: You're speaking plain HTTP to an SSL-enabled server port. Instead use the HTTPS scheme to access this URL, please.   There seem to be a lot of somewhat similar questions, however I am unable to find one that actually answers my question.
17360
I hope that title is clear.  How do I prevent HTTPS requests for non-ssl-enabled virtual hosts from going to the first ssl-enabled virtualhost (setup is Apache-SNI).  For example, using my abbreviated config below, requests for https://example.com (a non-ssl vhost) are being served by Apache at the ssl-enabled vhost https://example.org. I'd like to disable that behavior and possibly reply with the appropriate HTTP response code (unsure of what that is).  It may not even be possible, but I thought I'd ask.  # I actually have a SNI setup, but it's not demonstrated here. # I don't think it's relevant in this situation.  NameVirtualHost *:80 NameVirtualHost *:443  &lt;VirtualHost *:80&gt;     ServerName example.org &lt;/VirtualHost&gt;  &lt;VirtualHost *:443&gt;     ServerName example.org &lt;/VirtualHost&gt;  &lt;VirtualHost *:80&gt;     ServerName example.com &lt;/VirtualHost&gt;   EDIT: Maybe a mod_rewrite rule in the first ssl-vhost?
61455
I create landing pages in order to launch PPC campaigns for my customers. However, I would like to host them all together under a sub-domain of MY website.   For example:  I want that someone who visits www.clientnumber2.com/landingpage could see the landing page and still the same URL www.clientnumber2.com/landingpage, but actually host it myself.  The same for client3, client4, and so on...
105731
Is there a way to host multiple domains with Apache web server without making any changes to the DNS server?  I have full control over the Apache server and no control over the DNS server.
112718
The Problem  Accessing my site over https (the only protocol allowed) I get the content, but none of the CSS, images etc.  Drupal is creating pages in response to https requests that include http links to these resources, but it should be using https.  What I've done  I have copied a site to a dev server. The site loads and basically works fine - I can log in etc. It's just that all the links drupal generates are http. The site I've copied it from also runs over https. The site does not exist on http (it would just get a Forbidden error). I've drush cc all.  So Apache's working - I can access the site. .htaccess is working (clean urls work, for example).  I'm using SNI to access the site because the server has other vhosts too, but I'm only accessing the site using the latest Firefox (and as it's a dev site and I'm the only dev, nobody else will use it).  I've done this dozens of times and am quite stumped! Why does Drupal not notice that the request came over https?  The fix  Turns out that .htaccess has this to say:   /* Base URL (optional).                                                          If Drupal is generating incorrect URLs on your site, which could             be in HTML headers (links to CSS and JS files) or visible links on pages     (such as in menus), uncomment the Base URL statement below (remove the       leading hash sign) and fill in the absolute URL to your Drupal installation.    Sure enough, putting $base_url = 'https://example.com'; fixed it.  But why is this necessary?
79738
I'm getting mixed messages online regarding SSL support for a Force.com site that is branded with a custom URL domain:   These two articles,  and , seem to suggest that you can register a force.com domain, mycompany.secure.force.com as a CNAME record for a branded domain, www.mycompany.com. On the other hand this idea, , suggests HTTPS is not supported yet.   Assuming SF cannot support HTTPS yet, what can be done to brand the URL, if at all possible?
119168
I am running into a weird problem trying to disable HTTPS for one domain, but the other domain has HTTPS. They both are different websites running on a dedicated server, sharing the same IP address for the domains.  However, I have a domain that does not have a SSL certificate, but the other does. I want to disable HTTPS for the non-certified domain while leaving the other domain with HTTPS on.  I have two different separate vhosts in /etc/nginx/sites-enabled/,   domain1.org (no HTTPS)  server {      listen                      80;     server_name                 www.domain1.org domain1.org;     root                        /var/www/domain1.org;     index                       index.html index.php index.htm;      error_log                   /var/www/logs/domain1.errors.log;      [ ... ]   domain2.com (with HTTPS)  server {      listen                      443 ssl;     server_name                 domain2.com www.domain2.com;      # INCLUDE SSL CERTIFICATE     include                     sites-enabled/domain2_ssl_include;       root                        /home/domain2/www/www;     index                       index.html index.php index.htm;      [ ... ]   I've included a listener to the port 443 for domain1.org, but once I do that, I get an aborted error from Firefox saying (when accessing ):     This Connection is Untrusted      You have asked Firefox to connect securely to domain1.org, but we can't confirm that your connection is secure.   I opened the technical data, it appears that the domain1.org is using the domain2.com SSL certificate:     domain1.org uses an invalid security certificate.      The certificate is only valid for the following names:    *.domain2.com , domain2.com        (Error code: ssl_error_bad_cert_domain)   So I added this to domain1.org vhost configuration:  server {      server_name                 domain1.org www.domain1.org;      listen                      443 ssl;      rewrite ^ http://domain1.org permanent; }   Which still gets me prompted with the Firefox error.  Now... when I access to , I get an 400 error from nginx saying this:     400 Bad Request      The plain HTTP request was sent to HTTPS port   I am not entirely sure what to do, disabling the https with ssl off; has no effect. How can I actually disable HTTPS for domain1.org but not for domain2.com?  I am using Ubuntu 12.04 running nginx 1.2.6.
29186
What are the pros and cons of having http://www.example.com/ vs http://example.com/?  For example a problem I'm aware of is that if I use a domain without www I can't set a cookie for the current subdomain only (since there is no subdomain), and the cookies I set will be sent to all subdomains.
103357
I've got a wildcard SSL certificate for *.example.com. I'm using Nginx, and redirecting all traffic for HTTP to HTTPS, and also rewriting the URLs to remove a www subdomain (if there is one). So it has,  http://subdomain.example.com       ---&gt; https://subdomain.example.com http://www.subdomain.example.com   ---&gt; https://subdomain.example.com https://www.subdomain.example.com  ---&gt; https://subdomain.example.com https://subdomain.example.com      ---&gt; https://subdomain.example.com  However, since my cert is for *.example.com, case 3 gets an SSL error in chrome (&quot;This is probably not the site that you are looking for!&quot;), but if you click through it gets redirected and all is well. I understand why, since the initial connection is for HTTPS with a www (2 levels of subdomains), which doesn't match what is on the wildcard certificate. I thought a solution would be to get an additional cert for *.*.example.com to cover www.*.example.com.  But it seems like that won't work. I spoke to agents from Namecheap and Comodo, and both said *.*.example.com was not possible. I also came across  that states:  Will SSL work with multilevel wildcards? With the distribution of Firefox 3.5, all major browsers allow only a single level of subdomain matching with certificate names that contain wildcards, in conformance with RFC 2818. In other words the certificate *.mydomain.com will work for one.mydomain.com or two.mydomain.com but NOT one.two.mydomain.com.  Is there a solution to this? To be able to cover www.*.example.com?