On 8/12/2010 9:33 AM, Phil Howard wrote:
No backup staff ... ouch.
budget cuts? :)
If they have load balancing, the restarts can be made transparent.
Just disable the server from the load balancer, wait the prescribed
honestly, this is so far out of my area that I don't get involved. They
On 8/12/2010 6:28 AM, Phil Howard wrote:
Our current site is here on server F (failing server):
It looks like a whole different subnet, so I assume it is running
within your department.
Nope, different department with different admins. Plus, the
administrator for server F has taken a new jo
as all other
traffic on that interim server uses custom ports.
Does anyone see any glaring problems with that? It seems to work ok...
Thanks!
Mike
On 8/11/2010 4:27 PM, Mike Soultanian wrote:
Hi!
I have three servers, all of which are running Apache: F is the failing
server, P is the main pr
Hi!
I have three servers, all of which are running Apache: F is the failing
server, P is the main production server, and I is the interim server.
Our current site is here on server F (failing server):
http://cota.csulb.edu
That server is failing - I need to get the site off of that server
im
On 8/2/2010 11:10 AM, Joost de Heer wrote:
Change the DNS entry to point to the IP address of the new host.
Is that it? Sorry, I've never done this before so I have no idea what's
involved. Our school has their own DNS servers so is it just a matter
of having them point their DNS servers f
Hi everyone,
I'm not sure what this is called, but I work at CSULB and have a website
hosted there. Problem is that we're using ColdFusion on-campus and
they're phasing out support for that platform.
So, I'm going to move the site off-campus, but I need to make sure that
when a user goes to
Well, I tried the following:
Redirect 301 /~music "http://www.csulb.edu/music";
And it worked. So I guess problem solved!
thanks,
Mike
On 5/17/2010 11:31 AM, Mike Soultanian wrote:
Hello,
I'm trying to redirect everyone that goes to http://www.csulb.edu/~music
over to http:
Hello,
I'm trying to redirect everyone that goes to http://www.csulb.edu/~music
over to http://www.csulb.edu/depts/music (no tilde) using the following
.htacess file:
Options +FollowSymLinks
RewriteEngine on
RewriteRule ^(.*)$ http://www.csulb.edu/music/$1 [L,NC,R=301]
I'm having mild success
Hi,
I am running Apache on a Windows Server and I would like to move my web
root to our file server (also running Windows Server). I was hoping
someone has done this before and could provide a few tips on how to do
this correctly? From what I've gathered, this is what I think I'd need
to do:
Torsten Foertsch wrote:
If you look for something that follows your HTML more closely have a
look at mod_proxy_html (http://apache.webthing.com/mod_proxy_html/). It
can distinguish between
Ok, after a LOT of futzing around with other ideas and examples, I
tweaked another example off the web
André Warnier wrote:
I mean, if in your browser you get such a response page, and look at the
html source of the page, do you really see links to
"http://myserver.tld:81/...";, or are they more like
yup.. that's exactly what I'm getting :(
Per my initial requirements, I was able to get reverse proxy working
pretty well so my legacy web app sees every request originating from
itself. To do this, I'm using the following:
proxyrequests off
NameVirtualHost *:80
NameVirtualHost myserver.tld:81
ProxyPass / http://myserver.tld:81/
P
Eric Covener wrote:
On Tue, Jan 13, 2009 at 2:55 AM, Mike Soultanian wrote:
Does anyone know how to tweak my rewrite such that it will forward
correctly, regardless of whether or not the folder has a trailing slash?
ProxyPassReverse would fix the redirect that's being se
I have a virtual host that accepts all traffic on port 80 and then
forwards that traffic to another virtual host on port 81:
RewriteRule /(.*) http://localhost:81/$1 [P,L]
It works great except when I leave off the backslash. So, for example,
"http://foobar.com/"; works correctly and so does
Justin Pasher wrote:
If you have more (sub)domains that point to the same virtualhost, then
you won't be able to use the above directive as-is, since it's
designed to funnel ALL requests through www.csulb.edu. It's mainly
designed for sites that have a handful of alias domains, but only one
Justin Pasher wrote:
Ahhh... Now it should actually be possible. If possible, I would
(personally) try to push all traffic to www.csulb.edu whenever they
try to pull csulb.edu. Whether or not this is possible in your
situation, I do not know. Something like this in the VirtualHost
config wou
Justin Pasher wrote:
Actually, ignore everything I just said. All this time I thought that
was what apache was doing, but it's actually occurring after the
mismatched server name warning is presented. The rewrite rule will
still catch the request and redirect them to https://www.csulb.edu,
Justin Pasher wrote:
You can simplify this a bit by saying "redirect anything that is not
going to www.csulb.edu". However, you'll have to put the rewrite
directives inside the configuration for the SSL version
of the site, as the .htaccess file is run after a connection is
established wi
Eric Covener wrote:
On Mon, Sep 29, 2008 at 4:25 PM, Mike Soultanian <[EMAIL PROTECTED]> wrote:
So, is it possible to set up a rewrite condition such that when someone
tries to navigate to https://csulb.edu, it will automatically redirect the
user to https://www.csulb.edu and avo
Our campus has an SSL certificate for www.csulb.edu. If you go to
https://www.csulb.edu everything works peachy.
Now, if you go to https://csulb.edu, you get an error. I talked to our
server admin and he said it's because our certificate is registered to
www.csulb.edu and not csulb.edu. He
eRule (.*) http://%{HTTP_HOST}%{REQUEST_URI}
Thanks!!
Mike
|
Mike Soultanian wrote:
Well, I think I kinda got it, but it doesn't seem to work right:
RewriteEngine On
RewriteCond %{QUERY_STRING} ssl=true [NC]
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
So, I would think that should
sed before to force full-time SSL
and never had these issues:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}
and the only thing I changed was the rewrite condition... er...
any help would be much appreciated!!
Thanks!
Mike
Mike Soultanian w
Hey Everyone,
I currently run phpbb and there is no facility to force SSL during
logins only - it's only full-time SSL or not. Because I have to encrypt
logins, I do the following in my .htaccess file:
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_UR
rys.com | habitatlife.com | selfgnosis.com
On Jul 19, 2006, at 5:47 PM, Mike Soultanian wrote:
Well, for example, I would like to be able to input either of the
following into my browser:
http://cfdev.cota.csulb.edu/cota
or
http://cfdev.cota.csulb.edu/cota/
and the web page will be displayed whi
Well, for example, I would like to be able to input either of the
following into my browser:
http://cfdev.cota.csulb.edu/cota
or
http://cfdev.cota.csulb.edu/cota/
and the web page will be displayed while the application server handling
the requests all see localhost as the originating addres
http://localhost:81/$1$2
you need the second dollar variable to pick up the second pair of
brackets, instead of always appending a slash.
Mike Soultanian wrote:
Boysenberry Payne wrote:
How about adding this:
RewriteRule /(.*)(/)?$ http://localhost:81/$1/ [P]
That almost worked!
That's i
Is there a way to make the proxy or rewrite mods only respond on a given
port. I have two active ports, 80 and 81, yet I only want the proxy
responding to port 80 requests. Is this easy to accomplish via
configuring the httpd.conf?
Thanks,
Mike
--
You know, I'm guessing that I'm getting that proxy loop error because
the proxy is listening on both ports 80 and 81 (I have a virtual host on
81)? Just a guess....
mike
Mike Soultanian wrote:
See the ProxyPassReverse directive, whose job it is to correct
trailing-slash redire
See the ProxyPassReverse directive, whose job it is to correct
trailing-slash redirects.
(Hint: You don't even need RewriteRule for this. ProxyPass will do fine.)
Joshua.
Hey Joshua,
For kicks I tried ProxyPass (I really have no idea what I'm doing) using
the following:
proxyrequests off
Pr
Boysenberry Payne wrote:
> How about adding this:
>
> RewriteRule /(.*)(/)?$ http://localhost:81/$1/ [P]
>
That almost worked!
That's interesting because it gets me through to the page, but still
leaves off the trailing slash. That in turn breaks the relative links
which are looking for the t
Hello,
We have to proxy our requests on our web server but we're running into
some problems. I'm having a problem with the following rewrite rule:
RewriteRule /(.*) http://localhost:81/$1 [P]
If I do not specify the trailing slash when using a folder name, I get
an error. So, for example, i
31 matches
Mail list logo
