Hello Eric,
I have opened a Bug for this issue - Bug
69344<https://bz.apache.org/bugzilla/show_bug.cgi?id=69344>
Regards,
Dev
From: Eric Covener
Sent: Saturday, September 14, 2024 12:35 AM
To: users@httpd.apache.org
Subject: Re: FW: [users@httpd] rewrite rule issue with Apache 2.4
a singh wellsfargo. com. INVALID> Sent: Tuesday, September 10, 2024 9: 45 PM To:
> users@ httpd. apache. org
>
> Hi Eric,
>
>
>
> Looks like mail was not posted on time. Re-attempting.
>
>
>
> Kindly review. Thanks.
>
>
>
> Regards,
>
&g
. Re-attempting.
Kindly review. Thanks.
Regards,
Dev
From: Daiya, Devendra singh
mailto:devendra.s.da...@wellsfargo.com.INVALID>>
Sent: Tuesday, September 10, 2024 9:45 PM
To: users@httpd.apache.org<mailto:users@httpd.apache.org>
Subject: RE: FW: [users@httpd] rewrite rule issue
Hi Eric,
Looks like mail was not posted on time. Re-attempting.
Kindly review. Thanks.
Regards,
Dev
From: Daiya, Devendra singh
Sent: Tuesday, September 10, 2024 9:45 PM
To: users@httpd.apache.org
Subject: RE: FW: [users@httpd] rewrite rule issue with Apache 2.4.62
Hi Eric, Below are Traces
id#7fc5a8004f80/initial] setting
lastsub to rule with output /launchpad.html
[Thu Sep 05 06:17:05.862711 2024] [rewrite:trace2] [pid 3531713:tid 3531735]
mod_rewrite.c(505): [client 123.11.22.345:9812] 123.11.22.345 - -
[xct-launchpad-dev.domain.com/sid#7009f8][rid#7fc5a8004f80/initial] forc
On Mon, Sep 9, 2024 at 1:25 PM Daiya, Devendra singh
wrote:
>
> Hi Eric, Team,
>
>
>
> We tested our application with 2.4.62 pointing to older version of
> mod_rewrite.so module (2.4.59) and application is working fine.
>
>
>
> Could you please let us know if there are any limitation defined in
To: users@httpd.apache.org
Subject: RE: FW: [users@httpd] rewrite rule issue with Apache 2.4.62
Hi Eric, For both versions, we have the same config. Below are the end-to-end
files. httpd. conf #HTTPD. CONF #TEMPLATE? ServerName xyz. hostname. com Listen
1098 LoadModule mpm_event_module modules
oto--)/(.*)([0-9]\.glb.wellsfargo.net)/?
$1/${map-file:${lowercase:$2}|$2}$3
Regards,
Dev
From: Eric Covener
Sent: Wednesday, August 28, 2024 7:17 PM
To: users@httpd.apache.org
Subject: Re: FW: [users@httpd] rewrite rule issue with Apache 2.4.62
> Is there
<mailto:devendra.s.da...@wellsfargo.com>
From: Eric Covener
Sent: Wednesday, August 28, 2024 7:17 PM
To: users@httpd.apache.org
Subject: Re: FW: [users@httpd] rewrite rule issue with Apache 2.4.62
> Is there anything we need to update in config file for Rewrite rule? I
> responded last week with follow
> Is there anything we need to update in config file for Rewrite rule?
I responded last week with followup questions.
-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.
Hi All,
For below issue, any leads would be of great help.
Is there anything we need to update in config file for Rewrite rule?
Thanks.
Regards,
Dev
From: Daiya, Devendra singh
Sent: Friday, August 23, 2024 8:49 PM
To: users@httpd.apache.org
Subject: [users@httpd] rewrite rule issue with
> Could you please review this case and let us know if we need to adjust any
> configuration with 2.4.62 version.
>
> 2.4.62 (failing to error.html)
>
> [Mon Aug 19 14:14:47.360450 2024] [rewrite:trace4] [pid 1177:tid 11999]
> mod_rewrite.c(505): [client :] - -
> [cci-launchpad-dev.hostname.com
Hi Team,
We are facing issues with rewrite rule, post migrating from 2.4.59 to 2.4.62.
We faced similar issues with 2.4.60/61 as well.
We are using below rewrite rules:
Below are set in httpd.conf file: -
RewriteRule ^--proto--/--error-- \
/launchpad.html [PT,L]
RewriteRule ^(--proto--/.*)-
Thank you for
your cooperation.
From: Frank Gingras
Sent: Monday, July 11, 2022 3:11 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] rewrite rule with ProxyPass and ProxyPassReverse
Typically, the solution is to avoid adding the double slashes to begin with. If
you show us your
Typically, the solution is to avoid adding the double slashes to begin
with. If you show us your Proxy* directives, we can comment further.
On Mon, 11 Jul 2022 at 15:45, wrote:
> I am not an HTTPD expert and am running into issues where double-slashes
> are being added to the end of the ProxyPas
I am not an HTTPD expert and am running into issues where double-slashes are
being added to the end of the ProxyPass and/or ProxyPassReverse statements in
our mod_proxy configuration. What is the proper way to handle this issue with
RewriteRules?
Thanks,
Dream * Excel * Explore * Inspire
Jon M
Eric,
My below configuration is just going to jump the url from
http://rm.jco.com.cn/myjco/orders/ to
https://rm.jco.com.cn/myjco/orders/
But it leads to infinite rewrite loop inside apache
RewriteCond %{SERVER_PORT} !^443$
RewriteCond %{HTTP_HOST} ^rm.jco.com.cn$
RewriteCond %{REQ
On Wed, Jul 15, 2015 at 12:32 PM, javalishixml wrote:
> RewriteCond %{REQUEST_URI} ^/myjco/mySecurity
You probably meant to negate this one, specifically to avoid the loop?
--
Eric Covener
cove...@gmail.com
-
To unsubscribe,
Hi Gurus,
Just a silly question this is. But I really suffer it too much ... :(
I'm using rewrite module to do rewrite url. I made below rule:
RewriteCond %{SERVER_PORT} !^443$
RewriteCond %{HTTP_HOST} ^www.jco.com.cn$
RewriteCond %{REQUEST_URI} ^/myjco/mySecurity
RewriteRule (.*) https:/
Hi everybody, I'm having a problem configuring a rewrite rule for my site.
I'm using apache 2.2.22 on Debian 7.
I used to have a single site under /var/www/Intranet/public. The former
rewrite rule configuration was on an .htaccess file in said directory
having the following:
SetEnv APPLICATION_E
On Fri, Jul 25, 2014 at 2:33 PM, Nick Edwards
wrote:
> Howdy,
> I've sent this to the roundcube list few days ago, no-one replied so ,
> since its also apache related, I'll ask here.
>
>
>
> Trying to understand the new "security" rules in .htaccess
>
> - deny access to files not containing a d
Howdy,
I've sent this to the roundcube list few days ago, no-one replied so ,
since its also apache related, I'll ask here.
Trying to understand the new "security" rules in .htaccess
- deny access to files not containing a dot or starting with a dot
# in all locations except installer direct
RewriteCond %{QUERY_STRING} ^action=cs_query$
RewriteRule ^/cgi-bin/blt?action=cs_query$ - [G]
Very close with this one ... Try:
RewriteCond %{QUERY_STRING} ^action=cs_query$
RewriteRule ^/cgi-bin/blt$ - [G]
As I said before, you can't include the query string in RewriteRule
state
>
>
> RewriteCond %{QUERY_STRING} ^action=cs_query$
> RewriteRule ^/cgi-bin/blt?action=cs_query$ - [G]
>
> Very close with this one ... Try:
RewriteCond %{QUERY_STRING} ^action=cs_query$
RewriteRule ^/cgi-bin/blt$ - [G]
As I said before, you can't include the query string in RewriteRule
sta
I tried the following thing without success.
RewriteEngine on
RewriteRule ^/cgi-bin/blt?action=cs_query$ - [G]
mod_rewrite matches the URi not the the query string. Read about
RewriteCond here:
http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritecond
I tried
RewriteCond
>
>
> I tried the following thing without success.
>
> RewriteEngine on
> RewriteRule ^/cgi-bin/blt?action=cs_query$ - [G]
>
> mod_rewrite matches the URi not the the query string. Read about
RewriteCond here:
http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html#rewritecond
Hi
I encounter problems to rewrite a rule
The page /cgi-bin/blt?action=cs_query
is now gone and I would like to notify this.
I tried the following thing without success.
RewriteEngine on
RewriteRule ^/cgi-bin/blt?action=cs_query$ - [G]
An idea ?
I tried with \? without success.
I have othe
On Fri, Aug 23, 2013 at 7:44 AM, vicky wrote:
> I would like to redirect the request from apache to tomcat using the URL
> http://dev.market.bills.com/
>without mentioning any context root in this url ,the request should get
> directed using the above URL to /food-bils application
> which is d
I would like to redirect the request from apache to tomcat using the URL
http://dev.market.bills.com/
without mentioning any context root in this url ,the request should get
directed using the above URL to /food-bils application
which is deployed on Tomcat
Kindly suggest what is the issu
Hi,
I have below similar rewrite rule in my conf -
---
RewriteCond %{HTTP_HOST}
^abc.xyz.com|^abc$
RewriteCond %{REQUEST_URI} !^/abc/.*
RewriteRule
^(.*)$ http://xyz.com/test/
[E=HTTP_REFERER:%{HTTP_REFERER},L]
---
If i hit, abc.xyz.com or abc - it redirects as per ru
Hi Vincenzo!
Thank you for this advise as well
By the way, I have added you in skype if you allow me.
Tamer
On 07/22/13 18:00, Vincenzo D'Amore wrote:
> Hi,
>
> happy to hear you have figured out at last :)
>
> For the future, if you're in trouble trying to understand what's wrong
> in yo
Hi,
happy to hear you have figured out at last :)
For the future, if you're in trouble trying to understand what's wrong in
your rewrite, if you can, try to enable RewriteLog it will help really a
lot.
Best regards,
Vincenzo
2013/7/21 Tamer Higazi
> Solved!
>
> My rewrite rules now look lik
Solved!
My rewrite rules now look like this:
RewriteEngine on
RewriteCond %{REQUEST_URI} !/static/
RewriteRule ^(.+)\.(css|img|fonts|js)$ /static/$1 [L]
RewriteCond $1 !^(index\.php|images|robots\.txt|static)
RewriteRule ^(.*)$ /index.php/$1 [L]
On 07/21/13 20:34, Tamer Higazi wrote:
> Hi Vin
Hi Vincenzo!
My rewrite rule now lookes like this:
RewriteEngine on
RewriteRule ^/(css|js|fonts)(/.*)?$ /static$2 [L]
RewriteRule ^/(.*)$ /index.php/$1 [L]
and now nothing works :(
If you have any further ideas, I would thank you.
Tamer
On 07/21/13 10:46, Vincenzo D'Amore wrote:
> Hi,
>
>
Hi,
IMHO the first rewrite doesn't match because regex is wrong.
The URL your rewrite should match is something like this:
/css/path/filename.css
so your regex should first match the first / character.
Then, don’t confuse alternation with a character class. If you want express an
alternation
Hi people!
I have problems making successfully a rewrite rule for my Webapplication
(CodeIgniter) with mod_rewrite.
In my ".htaccess" file, I have the following rewrite rules:
RewriteEngine on
RewriteRule ^[css|js|fonts](/.*)?$ /static$1 [L]
RewriteRule ^(.*)$ /index.php/$1 [L]
But the 1st rule
Hi Guys,
My configuration is Apache/2.2.23 on CentOS x86_64, running Subversion
server. Recently I installed SSL certificates and I want to redirect all
request comming to http://myhostname.domain.com/svn/reponame to be
redirected to https://myhostname.domain.com/svn/reponame automatically.
This c
On Apr 25, 2013, at 9:53 PM, "Chris Arnold" wrote:
>
>
> From: "Chris Arnold"
> To: users@httpd.apache.org
> Sent: Thursday, April 25, 2013 4:29:15 PM
> Subject: Re: [users@httpd] Rewrite Rule
>
> On Apr 25, 2013, at 3:29 PM, "Chris Arnold&qu
- Original Message -
From: "Chris Arnold"
To: users@httpd.apache.org
Sent: Thursday, April 25, 2013 4:29:15 PM
Subject: Re: [users@httpd] Rewrite Rule
On Apr 25, 2013, at 3:29 PM, "Chris Arnold" wrote:
> Ok, I got namevirtualhost working on 443. I also ma
On Apr 25, 2013, at 3:29 PM, "Chris Arnold" wrote:
> Ok, I got namevirtualhost working on 443. I also made a new VirtualHost as
> you instructed above. In fact, https://apps.domain.tld does make it to the
> other server, 192.168.123.7. Now the problem is the proxied url does not
> complete, it
On Apr 25, 2013, at 12:36 PM, "Tom Evans" wrote:
> On Thu, Apr 25, 2013 at 4:53 PM, Chris Arnold
> wrote:
>> On Apr 25, 2013, at 11:32 AM, "Tom Evans" wrote:
>>
>> Because reverse proxy does not work
>
> ...
>
> The *only* way to get content from a backend is via reverse proxy.
>
>>
>> As I
hursday, April 25, 2013 12:39:47 PM
Subject: Re: [users@httpd] Rewrite Rule
On Thu, Apr 25, 2013 at 4:53 PM, Chris Arnold
wrote:
On Apr 25, 2013, at 11:32 AM, "Tom Evans" wrote:
It looks like you are rewriting it to it's current location. This
leads to a loop.
Why are you usin
ficate name not matching.
> Also in this present config, webmail stops working and ifolder stops working.
> These are in the "main" ssl virtualhost and you access them by
> https://mail.teknerds.net and https://teknerds.net/ifolder. I am going to
> undo the listen.conf edit and ren
or the help
- Original Message -
From: "Tom Evans"
To: users@httpd.apache.org
Sent: Thursday, April 25, 2013 12:39:47 PM
Subject: Re: [users@httpd] Rewrite Rule
On Thu, Apr 25, 2013 at 4:53 PM, Chris Arnold
wrote:
> On Apr 25, 2013, at 11:32 AM, "Tom Evans" wrote:
>
&
On Thu, Apr 25, 2013 at 4:53 PM, Chris Arnold
wrote:
> On Apr 25, 2013, at 11:32 AM, "Tom Evans" wrote:
>
>> It looks like you are rewriting it to it's current location. This
>> leads to a loop.
>>
>> Why are you using rewrite rules anyway?
>
> Because reverse proxy does not work
...
The *only*
On Apr 25, 2013, at 11:32 AM, "Tom Evans" wrote:
> It looks like you are rewriting it to it's current location. This
> leads to a loop.
>
> Why are you using rewrite rules anyway?
Because reverse proxy does not work
> It seems like you want to
> reverse proxy from an apache server with a publi
On Thu, Apr 25, 2013 at 4:13 PM, Chris Arnold
wrote:
>
>
> From: "Chris Arnold"
> To: users@httpd.apache.org
> Sent: Wednesday, April 24, 2013 3:21:25 PM
> Subject: Re: [users@httpd] Rewrite Rule
>
>
> On Apr 24, 2013, at 2:00 PM, "Chris Arnold"
From: "Chris Arnold"
To: users@httpd.apache.org
Sent: Wednesday, April 24, 2013 3:21:25 PM
Subject: Re: [users@httpd] Rewrite Rule
On Apr 24, 2013, at 2:00 PM, "Chris Arnold" wrote:
> On Apr 23, 2013, at 8:39 PM, "Chris Arnold" wrote:
>
> >
On Apr 24, 2013, at 2:00 PM, "Chris Arnold" wrote:
> On Apr 23, 2013, at 8:39 PM, "Chris Arnold" wrote:
>
> > Apache 2.12.x on SLES11 SP2. We have a RDS server behind an apache server
> > using proxypass. We need users to get to the RDS server using
> > https://apps.domain.tld. The apache serv
On Apr 23, 2013, at 8:39 PM, "Chris Arnold" wrote:
> Apache 2.12.x on SLES11 SP2. We have a RDS server behind an apache server
> using proxypass. We need users to get to the RDS server using
> https://apps.domain.tld. The apache server should catch this request and
> send/rewrite to
> https:/
Apache 2.12.x on SLES11 SP2. We have a RDS server behind an apache server using
proxypass. We need users to get to the RDS server using
https://apps.domain.tld. The apache server should catch this request and
send/rewrite to https://apps.domain.tld/rds/something/something/login.whatever.
We hav
On Apr 19, 2013, at 4:48 AM, "Pete Houston" wrote:
> On Mon, Apr 15, 2013 at 06:57:13PM -0400, Chris Arnold wrote:
>> We have a server at http://rootsite.net. We also have another site/app that
>> runs at http://apps.rootsite.net. We host client applications on our server
>> using apache so the
On Mon, Apr 15, 2013 at 06:57:13PM -0400, Chris Arnold wrote:
> We have a server at http://rootsite.net. We also have another site/app that
> runs at http://apps.rootsite.net. We host client applications on our server
> using apache so the above site/app needs to be
> http://apps.ourclientsdomai
On Apr 15, 2013, at 7:51 PM, "Chris Arnold" wrote:
> On Apr 15, 2013, at 7:41 PM, "Daniel Ruggeri" wrote:
>
> > On 4/15/2013 6:34 PM, Chris Arnold wrote:
> >> Actually, it is the RedirectMatch specifically causing the problem. How to
> >> specify only match http://apps.somesite.tld?
> >
> > Yo
On Apr 15, 2013, at 7:41 PM, "Daniel Ruggeri" wrote:
> On 4/15/2013 6:34 PM, Chris Arnold wrote:
>> Actually, it is the RedirectMatch specifically causing the problem. How to
>> specify only match http://apps.somesite.tld?
>
> You can't. You have to use RewriteCond (as you have) and then use
>
On 4/15/2013 6:34 PM, Chris Arnold wrote:
> Actually, it is the RedirectMatch specifically causing the problem. How to
> specify only match http://apps.somesite.tld?
You can't. You have to use RewriteCond (as you have) and then use
"RewriteRule ^/$ /somealias/" in place of the RedirectMatch that
On Mon, Apr 15, 2013 at 6:57 PM, Chris Arnold
wrote:
> We have a server at http://rootsite.net. We also have another site/app that
> runs at http://apps.rootsite.net. We host client applications on our server
> using apache so the above site/app needs to be
> http://apps.ourclientsdomain.tld. H
On Mon, Apr 15, 2013 at 6:57 PM, Chris Arnold
wrote:
> We have a server at http://rootsite.net. We also have another site/app that
> runs at http://apps.rootsite.net. We host client applications on our server
> using apache so the above site/app needs to be
> http://apps.ourclientsdomain.tld. H
We have a server at http://rootsite.net. We also have another site/app that
runs at http://apps.rootsite.net. We host client applications on our server
using apache so the above site/app needs to be
http://apps.ourclientsdomain.tld. Here is what i have gotten to work in the
site/app virtual hos
I have an virtual host that is redirecting all requests from port 80 to
443. However, when doing this when there is an email in the url, for
example http://foo.tld/bar.php?email=User%40domain.tld gets redirected to
https://foo.tld/bar.php?email=User%2540domain.tld which tends to be a
problem. I
...@electrichendrix.com]
Sent: Tuesday, July 10, 2012 10:20 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Rewrite Rule Help (again)
In the event anyone comes across this, i got this to work using the following:
RewriteEngine On
RewriteCond %{HTTP_HOST} !^update.domain.com$ [NC
>
> ServerAdmin em...@domain.com
> ServerName domain.net
> ServerAlias www.domain.net
>
> #SSLProxyEngine On
> #ProxyPass /ifolder/ https://192.168.123.4/ifolder/
> #ProxyPassReverse /ifolder/ https://192.168.123.4/ifolder/
> RewriteEngine On
> RewriteRule ^/ifolder
On Wed, Jul 11, 2012 at 1:22 PM, Chris Arnold
wrote:
> >You may need to change the R to a P:
>
> >RewriteEngine On
> >RewriteCond %{HTTP_HOST} !^update.domain.com$ [NC]
> >RewriteRule ^/$ http://private.ip.address/ [P,L]
>
> This sends all http traffic to the private ip server
>
> >This turns the
>You may need to change the R to a P:
>RewriteEngine On
>RewriteCond %{HTTP_HOST} !^update.domain.com$ [NC]
>RewriteRule ^/$ http://private.ip.address/ [P,L]
This sends all http traffic to the private ip server
>This turns the rule into a proxy to that private IP, assuming that is
>what you are
On 7/10/2012 9:32 PM, Chris Arnold wrote:
> RewriteEngine On
> > RewriteCond %{HTTP_HOST} !^update.domain.com$ [NC]
> > RewriteRule ^/$ http://private.ip.address [R,L]
You may need to change the R to a P:
RewriteEngine On
RewriteCond %{HTTP_HOST} !^update.domain.com$ [NC]
RewriteRule ^/$ http://p
ing:
> RewriteEngine On
> RewriteCond %{HTTP_HOST} !^update.domain.com$ [NC]
> RewriteRule ^/$ http://private.ip.address [R,L]
>
>
> - Original Message -
> From: "Chris Arnold"
> To: users@httpd.apache.org
> Sent: Tuesday, July 10, 2012 9:37:30 PM
> S
y, July 10, 2012 9:37:30 PM
Subject: Re: [users@httpd] Rewrite Rule Help (again)
>You've been already given the answer by Eric what else do you need? Read
>mod_rewrite manual and combine RewriteCond and RewriteRule >commands thats all
>you need to do.
Igor,i have read the rew
>You've been already given the answer by Eric what else do you need? Read
>mod_rewrite manual and combine RewriteCond and RewriteRule >commands thats all
>you need to do.
Igor,i have read the rewrite guide and tried what i thought was needed. Which i
have repeated here more than 1 time but thi
You've been already given the answer by Eric what else do you need? Read
mod_rewrite manual and combine RewriteCond and RewriteRule commands thats
all you need to do.
On Jul 11, 2012 9:12 AM, "Chris Arnold"
wrote:
> Am I not asking the right question? Have I not given enough information?
> Or am
On Jul 10, 2012, at 6:11 PM, Chris Arnold wrote:
> Am I not asking the right question? Have I not given enough information? Or
> am I missing something?
>
> Sent from my iPhone
>
> On Jul 10, 2012, at 1:27 PM, Chris Arnold wrote:
>
>> Anybody got any ideas?
>>
>> Sent from my iPhone
>>
>>
Am I not asking the right question? Have I not given enough information? Or am
I missing something?
Sent from my iPhone
On Jul 10, 2012, at 1:27 PM, Chris Arnold wrote:
> Anybody got any ideas?
>
> Sent from my iPhone
>
> On Jul 9, 2012, at 7:24 PM, Chris Arnold wrote:
>
>> On Jul 9, 2012,
Anybody got any ideas?
Sent from my iPhone
On Jul 9, 2012, at 7:24 PM, Chris Arnold wrote:
> On Jul 9, 2012, at 6:28 PM, Daniel Ruggeri wrote:
>
>> On 7/9/2012 5:03 PM, Chris Arnold wrote:
>>> So the RewriteRule ^/$ http://192.168.123.2 [L]
>>> Sends all traffic to 192.168.123.2. I just need
On Jul 9, 2012, at 6:28 PM, Daniel Ruggeri wrote:
> On 7/9/2012 5:03 PM, Chris Arnold wrote:
>> So the RewriteRule ^/$ http://192.168.123.2 [L]
>> Sends all traffic to 192.168.123.2. I just need http://update.domain.com
>> traffic to go to the 192.168.123.2 host.
>
> Chris;
>I think more i
On 7/9/2012 5:03 PM, Chris Arnold wrote:
> So the RewriteRule ^/$ http://192.168.123.2 [L]
> Sends all traffic to 192.168.123.2. I just need
> http://update.domain.com traffic to go to the 192.168.123.2 host.
Chris;
I think more information is needed... how do clients get to
"update.domain.com
Anybody got any ideas?
Sent from my iPhone
On Jul 8, 2012, at 9:30 PM, Chris Arnold wrote:
> So the RewriteRule ^/$ http://192.168.123.2 [L]
> Sends all traffic to 192.168.123.2. I just need http://update.domain.com
> traffic to go to the 192.168.123.2 host.
>
>
>
> On Jul 7, 2012, at 11:5
So the RewriteRule ^/$ http://192.168.123.2 [L]
Sends all traffic to 192.168.123.2. I just need http://update.domain.com
traffic to go to the 192.168.123.2 host.
On Jul 7, 2012, at 11:50 AM, Chris Arnold wrote:
> On Jul 7, 2012, at 10:54 AM, Chris Arnold wrote:
>
That's the same as if
On Jul 7, 2012, at 10:54 AM, Chris Arnold wrote:
>>> That's the same as if it ended with a slash, and matched by ^/$
>
> Ok my host file has RewriteRule ^/$ http://update.domain.com [L]
> When I goto http://update.domain.com using safari, I receive:
> Response Error.
>
> Technical description:
>> That's the same as if it ended with a slash, and matched by ^/$
Ok my host file has RewriteRule ^/$ http://update.domain.com [L]
When I goto http://update.domain.com using safari, I receive:
Response Error.
Technical description:
502 Bad Gateway - Response Error, a bad response was received fr
On Tue, Jul 3, 2012 at 5:45 PM, Chris Arnold
wrote:
>>That's the same as if it ended with a slash, and matched by ^/$
>
> So, RewriteRule ^/$ http://192.168.123.2/ will send just
> http://updates.domain.com to 192.168.123.2? I don't want all http traffic to
> go to that server, just http://updat
>That's the same as if it ended with a slash, and matched by ^/$
So, RewriteRule ^/$ http://192.168.123.2/ will send just
http://updates.domain.com to 192.168.123.2? I don't want all http traffic to go
to that server, just http://updates.domain.com.
-
> but am not sure how to rewrite without a folder (ie http://updates.domain.com
> to another server with the same address).
That's the same as if it ended with a slash, and matched by ^/$
-
To unsubscribe, e-mail: users-unsubscr
Hello list! Apache 2.2.12 on SLES 11 SP2. I need to rewrite/proxy
http://updates.domain.com traffic to another server on the LAN. I have a few
rewrite rules in my host file now:
RewriteRule ^/folder http://%{HTTP_HOST}/folder/ [L]
but am not sure how to rewrite without a folder (ie http://update
On 02.03.2012, at 15:59, Vivek Nambiar wrote:
> http://servername:port/myapp then it should redirect itself to
> https://servername:SSLport/myapp.
>
> I have added the following rewrite condition and rule in my httpd.conf file
>
> RewriteCond %{SERVER_PORT} PORT
> RewriteRule ^/(.*)$ https://%{S
Hi,
Thank you and that works fine,but I would still like to know why rewrite
rule does not work.May be I am not using the write parameters??.
Regards
On Fri, Mar 2, 2012 at 9:08 PM, Mathijs wrote:
> The cleanest way of doing this, doesn't even need mod_rewrite. Just define
> two virtualhosts,
The cleanest way of doing this, doesn't even need mod_rewrite. Just define
two virtualhosts, one for the non-ssl host and one for the ssl host:
NameVirtualHost *:80
ServerName www.example.com
Redirect permanent / https://www.example.com/
NameVirtualHost *:443
ServerName www.example.co
On Thu, Jan 19, 2012 at 7:36 AM, Indraveni chebolu
wrote:
> My links are not absolute. They are all relative paths. When I am changing
> the RewriteRule then all my links are changing as written in rule rather
> than rendering as per accessed domain name.
mod_rewrite doesn't change the links in y
My links are not absolute. They are all relative paths. When I am changing
the RewriteRule then all my links are changing as written in rule rather
than rendering as per accessed domain name.
On Thu, Jan 19, 2012 at 4:27 PM, Eric Covener wrote:
> On Wed, Jan 18, 2012 at 11:20 PM, Indraveni chebo
On Wed, Jan 18, 2012 at 11:20 PM, Indraveni chebolu
wrote:
> The HTML look perfectly alright.
Doesn't look right to me, your links are all absolute URLs. They
aren't going to magically change when you access the server by IP
address.
-
The HTML look perfectly alright. If I change the URL to IP also it works
good. something like, I can access server.com/products ip/products, both
show up correctly.
You can check my site at http://cdachyd.in, as well the same with its Ip
http://196.12.45.103
When you access with cdachyd.in, all l
> IF I access server.com -> all links in my site are with server.com/products,
> server.com/services etc
>
> But I access with 192.168.52.58 -> site opens up well , but the links of the
> pages are server.com/products, server.com/services
>
> How can I resolve this ? I mean my site should be linked
Hi all,
I have configured apache in front of plone using rewrite rule, Similar
configuration as shown here
http://nathanvangheem.com/news/plone-with-apache-front-end-on-ubuntu
Site is working very fine. But have a small problem.
My plone site has all dynamic links, i.e with which ever URL i acc
91 matches
Mail list logo
