I have a website - www.domain.com - with Windows hosting. I don't want to install WordPress on Windows. Instead I want to get a WordPress blog on Linux hosting and create a virtual directory on my main server: www.domain.com/blog - which points to the WordPress blog. However, I can't find how to do this.
I have found documentation on how to create virtual directories in IIS 7.0, but this all seems to involve a directory on the same server.
Thanks, Jon
virtual directories are for running separate applications (different web roots, web.configs etc) on the same server as part of a single domain - so not what your looking for.
As Lex Li tersely pointed out, one option is you can use IIS as a proxy and rewrite the urls to some other host. IIS can modify the urls if nessersary so traffic appears to be served by your Windows server, when in fact IIS is making sneaky requests to the Linux blog behind the scenes and modifying the markup to ensure urls point to the Windows machine, and not the actual url which points to your linux box (your blog could be on any domain/subdomain/path and still appear to be part of yur site).
You could also use a CDN (cloudflare is free for the basic package...) and that allows you to setup rules so you can request content from different origin servers (ie your linux box) based on a prefix (/blog in your case), but all other traffic is sent to your Windows server.
Another option (not quiet what you asked for, but really simple to setup...) - if you can use a sub-domain instead of a prefix to the path (ie blog.domain.com/ instead of www.domain.com/blog) you can just point DNS for blog. to your linux host and www. to your IIS box - no configuration required to your Windows server.
Worth noting that its pretty much always a good idea to use a CDN infront of your web servers, its a layer of protection, makes your pages load faster etc etc etc (and it would work in front of either of the other 2 options suggested above)
Related
I yesterday received a zip file containing an old asp site from 2005. Its came in a folder called ivx.
I've unzipped ivx to c:\inetpub\wwwroot and then created an application in IIS called ivxapp and pointed it to c:\inetpub\wwwroot\ivx. Now when I type http://localhost/ivxapp, I am able to access the index page.
My problem is, whoever designed that site, designed it when IIS5 or IIS6 was around. He's used paths like more... which leads to http://localhost/new_posts.asp and not http://localhost/imagevertex/new_posts.asp
The whole site is some 21000 lines of code and contains many many references like this. Then comes the problem with <!--#include virtual = "/common/adminverify.asp" -->
Instead of having to manually edit the entire code, do you know a way to get things going?
This site worked perfectly well on a production server. Right now it's on my local machine on Windows 7 64 home premium.
Yes, you need to give this site a root-URL of its own, and not run it in a subdirectory of your localhost.
This is more of a web-administration question, but what you need to do is either run it under "localhost" directly, or add a domain-name to your network to run this site under.
The easiest for you right now is probably the first option.
If you aren't running a different site under localhost already:
Go to the IIS manager and click the 'localhost' site. On the right side of the IIS interface you can change the basic settings. Point the physical path to the ivx directory. You can reach the site directly on http://localhost.
If you are already running a site under localhost you need to keep:
Now, if you -are- already running a site on your localhost, the second easiest option is to run the ivx site under localhost, but on a different port. To accomplish that, click on the current ivx site in IIS, change the path in the same way as descibed above, and after that click on "bindings" in IIS, and change the PORT for the ivx site to something other than 80, for example 81.
The ivx site will then run on http://localhost:81, your current localhost will still run on http://localhost.
The hard way: adding a host to your network or PC:
The last option is to add a new hostname for the site to your network. You can add an A-record in your DNS for the ip-address of your server or add a host name to your HOSTS file in Windows on your server ("server" in the sense of the machine that runs the site, which can also be your local machine)
You can add a made-up name to the ip-address of the server, and in IIS' bindings add that name under "host name". this way you can run two different sites on the same machine, the "host name" seeting in IIS will make sure that calls to that specific hostname will reach the correct site. Adding it to the DNS of your network, or the HOST file in Windows will make sure the name is resolved to the correct machine (your webserver).
This last option is a little tricky of you've never done something like this before, but the first option works just as well.
Good luck!
Erik
I have set a plone product server with nginx + varnish + haproxy + 4 instance.(the buildout deploy configuration is come from the professional plone4 development book writted by Martin).
Now I have troubles with login process. I had to submit login info two times for signing in plone site.
I don't kown if nginx needs some settings like apache with mod_auth_ktk,or plone.session must adjust some parameters.
In fact , If I directly access instance using http://demo.com:8001/Plone address , it is OK.
Thanks.
There are potentially several causes of this problem, but the most common is a misconfiguration of the virtual hosting setup that causes some page resources to be served from a different URL than others.
View source on the browser, and look for differences in the URL between the page itself and the CSS/JS resources. If you find any, work on your virtual-hosting specifications.
I have two web site that are 99% similar. They share all of the same pages except the difference being that the logos change, a few of the links change, and the products that show up on either web site are flagged to show up on either or, or both. They use the same database.
I have written a utility method that essentially injects a where clause into any database access code I write throughout the app to determine which products to display depending on the current URL.
Problem: Website B gives the user a warning message that the site they are trying to go to is in fact Website A. I've read that the SSL cert needs a distinct IP.
Right now how I have everything set up is very clean on a maintenance perspective. I can update files in one place. Any suggestions on how to make the SSL behave, or am I looking at seperate IP's for the hosting(I really don't want to have to do this)?
If the latter, what do you suggest?
Site runs ASP.NET 4.0. Precompiled DLL.
UPDATE: Thanks to #GregS comment
If the sites share the same domain you can use a wildcard certificate
site1 - site1.somedomain.com
site2 - site2.somedomain.com
Otherwise you will need to get a UCC (United communications certificate) that will be for both domains.
You will need to configure IIS 7 from the command line because the GUI doesn't support setting different host headers for the same certificate. This tutorial shows how it can be done.
I setup another website in IIS that points to the same files as the first web site, got another SSL cert for the new site.
I don't want to pay for a domain, but simulate a url exists, something like 'www.myapplication.app'. Is this possible?
I'm guessing I need to configure some thing with IIS7 or something right?
This is for a college course and instead of just doing the bare minimum I'd like to make something very nice to show.
I realize this question might be broad but any links would be great. :) Especially if it starts from the beginning of IIS configuration.
My ultimate plan is to have a Windows Server 2008 on a Virtual Machine and publish it there, is it possible?
c:\windows\system32\drivers\etc\hosts
In this file you can mimic domains, for example you would put:
127.0.0.1 www.myapplication.com
Where 127.0.0.1 is always referring to you locally (== localhost)
Added obvious step:
You then create an application in IIS where you use this domain in the HostName of the application. You then can acccess your own domain from your browser.
I have a CMS application that manages multiple websites, today whenever i change the codebehind of one of these websites - i have to rebuild the dll for all websites, deploy it - this disconnects all current sessions and is really bad.
The iis is configured to listen to all domain requests, if the request is to one of the websites' domain , the application rewrites it, or example, if someone requests for http://www.example.com, and example.com is configured in the application to be website 12, it is rewritten to http://www.example.com/websites/12/default.aspx.
This is done for all websites.
We want to seperate the dlls of the websites from each other, and from the main CMS, we have a virtual directory to each websites, but when trying to rewrite to it, we discover that IIS support this (we get an "Could not load type '_12._Default'". error).
How can we perform this rewrite so it does rewrite to virtual directories, or if anyone has any other solution for the initial dll seperation problem.
Thanks in advance
You can easly do it with iis7
http://learn.iis.net/page.aspx/460/using-the-url-rewrite-module/
You could use a utility like http://iirf.codeplex.com to achieve this. It's easy to install, improved over past versions, and the owner of the project does respond pretty quickly to questions. Best of all, it's free, and supports global/virtual directory rewriting.
HTH.