September 26, 2003 (This post is more than 2 years old.)

Apache Virtual Hosts and CF

coldfusion

So, I ran into a problem this week. I was trying to use virtual hosts w/ CFMX under Apache for Windows. However, everytime I'd request a file on the second server that also existed on the first server, CF would run the file from the first server instead of the second server.

I double, triple checked my httpd.conf file but couldn't find anything wrong.

However, I had forgotten one of the first things you check when you run into problems - I was running an older version of Apache (2.0.44 instead of 2.0.47). As soon as I upgraded, it worked fine.

Support this Content!

If you like this content, please consider supporting me. You can become a Patron, visit my Amazon wishlist, or buy me a coffee! Any support helps!

Want to get a copy of every new post? Use the form below to sign up for my newsletter.

Archived Comments

Comment 1 by Tony Brandner posted on 9/26/2003 at 5:48 PM

So the problem goes away with the newest version of Apache? That's interesting.

We've been having the problem for a month or so, and it was driving us crazy. We fixed the problem by changing a setting in JRUN for multi-homed servers, but that causes CFMX to slow to a crawl.

It's kind of a catch-22.

Interestingly, now we find all sorts of people talking about this issue. Still no solutions that will fix our error.

We're not using Apache 2.x, and after these problems I think we're all a little nervous about making a change like that. What are your thoughts on Apache 1.x and 2.x? Would it be worth considering the change? Are there any other known issues with Apache 2.x and CF?

Comment 2 by Matt Liotta posted on 9/26/2003 at 6:58 PM

Considering that Apache 2.0.44 works fine with virtual hosts when not using CFMX, I believe the issue lies with CFMX and not Apache. I am glad upgrading to the latest version fixed your problem, but I don't think the real problem has been fixed yet in CFMX. For example, when the next version of Apache comes out that you decide to upgrade to will the problem repeat? Who knows, but obviously it is possible and that sucks.

Comment 3 by Raymond Camden posted on 9/26/2003 at 7:01 PM

Matt: Actually you are quite right. I noticed that any HTML request worked fine. Of course, maybe CFMX only supports 2.0.47? I'd have to check the docs and they are a bit hard to search so iI won't bother.

Tony: I'm not using Apache/Virtual Servers on a production box, but I can say that everything seems very zippy. I'm using IIS/Virtual Servers on a production box and everything runs just fine. I can't give you my thoughts re: Apache1/2 because I'm really just a neophyte at both. I use em - but just the simple features really, and I do not use it a on a production server. (Well, not w/ CF anyway.)

Comment 4 by Matt Knight posted on 9/26/2003 at 8:09 PM

I have tested CFMX 6.1 with Apache 1.3.X and 2.0.x, both with over 100 vhosts. The issue comes from CF caching the domain info from the request. There is an option to tell CF not to cache the domain info. Can't remember where I did it at (been a few months) but it fixed our problems right away.

Comment 5 by Matt Liotta posted on 9/26/2003 at 8:18 PM

Raymond should have probably mentioned that this was already discussed on a mailing list where he indicated that he did change the "cacherealpath" setting and still had the problem.

I also noticed the following blog entry from a Macromedia employee that seems to also think an Apache upgrade is a solution. I continue to disagree.

http://www.talkingtree.com/...

Support this Content!

Archived Comments

Webmentions