On Mon, Jun 21, 2010 at 1:14 PM, Matus UHLAR - fantomas
wrote:
> can you tell usa what are you trying to do?
I am trying to understand what ever was written on tutorial.
Nothing else.Since I could not understand so I posted.
-
T
On 15.06.10 18:12, Tapas Mishra wrote:
> http://http://www.askapache.com/htaccess/crazy-advanced-mod_rewrite-tutorial.html
>
> is a link to a tutorial which mentions following use of ReWriteRule is wrong.
>
> RewriteEngine On
> RewriteBase /
>
> RewriteCond %{HTTP_HOST} !^www\.askapache\.com$ [
Hi,Tom and Rich thanks for your links.Can you provide any more link as
what exactly can I do more with Apache.
I have hosted websites and know some bit of reverse proxy etc.
>From this discussion I got curiosity to understand the hooking process
of apache.Can you provide me some links which you fee
On Jun 15, 2010, at 8:42 AM, Tapas Mishra wrote:
http://http://www.askapache.com/htaccess/crazy-advanced-mod_rewrite-tutorial.html
is a link to a tutorial which mentions following use of ReWriteRule
is wrong.
Anything found on askapache.com should be taken with a great deal of
skepticism
On Tue, Jun 15, 2010 at 3:56 PM, Tapas Mishra wrote:
> On Tue, Jun 15, 2010 at 8:16 PM, Tom Evans wrote:
>>
>> I dont understand what you are asking? - the reply comes from apache.
> I could not understand I am newcomer to apache.I have used Reverse
> Proxy and other settings but do not completel
On Tue, Jun 15, 2010 at 8:16 PM, Tom Evans wrote:
>
> I dont understand what you are asking? - the reply comes from apache.
I could not understand I am newcomer to apache.I have used Reverse
Proxy and other settings but do not completely understand it.
So trying to understand how apache behaves wh
On Tue, Jun 15, 2010 at 3:41 PM, Tapas Mishra wrote:
>>
>> HTTP/1.0 clients do not send a Host header in the request
>> => no host information can be inferred from a request
>> => HTTP_HOST will be empty.
> but if HTTP_HOST is empty then from where is the reply coming from ?
>
I dont understand
>
> HTTP/1.0 clients do not send a Host header in the request
> => no host information can be inferred from a request
> => HTTP_HOST will be empty.
but if HTTP_HOST is empty then from where is the reply coming from ?
--
Tapas
http://mightydreams.blogspot.com
http://wiki.xensource.com/xenwiki/X
On Tue, Jun 15, 2010 at 3:33 PM, Tapas Mishra wrote:
> On Tue, Jun 15, 2010 at 6:49 PM, Eric Covener wrote:
>
>> *) You Should not redirect if HTTP_HOST is empty, for HTTP/1.0
>> clients, or you might loop.
>
> I could not understand your statement HTTP_HOST empty can you be a
> bit explanatory.
On Tue, Jun 15, 2010 at 6:49 PM, Eric Covener wrote:
> *) You Should not redirect if HTTP_HOST is empty, for HTTP/1.0
> clients, or you might loop.
I could not understand your statement HTTP_HOST empty can you be a
bit explanatory.It will help newbies like me.
--
Tapas
http://mightydreams.blo
On Tue, Jun 15, 2010 at 9:39 AM, Tom Evans wrote:
> On Tue, Jun 15, 2010 at 2:19 PM, Eric Covener wrote:
>> Who can guess if that silly page meant either of these subtle issues
>> with the recipe:
>>
>> *) ".+" in .htaccess won't match a request for "/", but I doubt that's
>> the operative part o
On Tue, Jun 15, 2010 at 2:19 PM, Eric Covener wrote:
> Who can guess if that silly page meant either of these subtle issues
> with the recipe:
>
> *) ".+" in .htaccess won't match a request for "/", but I doubt that's
> the operative part of the exercise.
> *) You Should not redirect if HTTP_HOST
On Tue, Jun 15, 2010 at 8:42 AM, Tapas Mishra wrote:
> http://http://www.askapache.com/htaccess/crazy-advanced-mod_rewrite-tutorial.html
>
> is a link to a tutorial which mentions following use of ReWriteRule is wrong.
>
> RewriteEngine On
> RewriteBase /
>
> RewriteCond %{HTTP_HOST} !^www\.askap
On Tue, Jun 15, 2010 at 1:42 PM, Tapas Mishra wrote:
> http://http://www.askapache.com/htaccess/crazy-advanced-mod_rewrite-tutorial.html
>
> is a link to a tutorial which mentions following use of ReWriteRule is wrong.
>
> RewriteEngine On
> RewriteBase /
>
> RewriteCond %{HTTP_HOST} !^www\.askap
http://http://www.askapache.com/htaccess/crazy-advanced-mod_rewrite-tutorial.html
is a link to a tutorial which mentions following use of ReWriteRule is wrong.
RewriteEngine On
RewriteBase /
RewriteCond %{HTTP_HOST} !^www\.askapache\.com$ [NC]
RewriteRule .+ http://www.askapache.com%{REQUEST_UR
Hi,
I was finally able to solve the problem.
The context root of application mingle was serving the site on / and not /mingle
so when some one requested http://site.mydomain.com/mingle he could
reach but not correct page.
Here is a link to a discussion which helped
http://community.thoughtworks.com
The application server when returns a URL then there is no /mingle in
URL so that might be a problem.
I am not clear as what to do with that.
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://
On Fri, Jun 11, 2010 at 9:01 PM, Tom Evans wrote:
> OK, that makes everything clearer.
>
> BTW, you are proxying /mingle/. That final / has meaning, please be
> precise about whether something has a trailing slash or not. Your
> first examples of attempting to access '/mingle/' through the proxy
I
OK, that makes everything clearer.
BTW, you are proxying /mingle/. That final / has meaning, please be
precise about whether something has a trailing slash or not. Your
first examples of attempting to access '/mingle/' through the proxy
were requesting the URL '/mingle', which is why you got 404s.
On Fri, Jun 11, 2010 at 5:50 PM, Tom Evans wrote:
> HTTP doesn't work on filenames. I need to understand what your sites
> are sending, whether requests are going to the right server, etc etc.
> Since I can't access your servers, and don't know your applications, I
> will have to describe how to
On Fri, Jun 11, 2010 at 12:18 PM, Tapas Mishra wrote:
>
> Does this give some clue?
Not really.
HTTP doesn't work on filenames. I need to understand what your sites
are sending, whether requests are going to the right server, etc etc.
Since I can't access your servers, and don't know your appli
On Fri, Jun 11, 2010 at 4:08 PM, Tom Evans wrote:
> On Fri, Jun 11, 2010 at 11:30 AM, Tapas Mishra wrote:
>> So let me know what you want to know.
>
>
> Does this not work for you?
No
>
> ServerName site1.mydomain.com
> ServerAdmin webmas...@localhost
>
> ProxyRequests off
>
> Or
On Fri, Jun 11, 2010 at 11:30 AM, Tapas Mishra wrote:
> So let me know what you want to know.
Does this not work for you?
ServerName site1.mydomain.com
ServerAdmin webmas...@localhost
ProxyRequests off
Order deny,allow
Allow from all
ProxyPreserveHost On
P
On Fri, Jun 11, 2010 at 2:10 PM, Tom Evans wrote:
> On Fri, Jun 11, 2010 at 8:44 AM, Tapas Mishra wrote:
>> On Thu, Jun 10, 2010 at 7:04 PM, Tom Evans wrote:
>>> Then your vhost should look like this:
>>>
>>>
>>> ServerName site1.mydomain.com
>>> ServerAdmin webmas...@localhost
>>>
>>>
On Fri, Jun 11, 2010 at 8:44 AM, Tapas Mishra wrote:
> On Thu, Jun 10, 2010 at 7:04 PM, Tom Evans wrote:
>> Then your vhost should look like this:
>>
>>
>> ServerName site1.mydomain.com
>> ServerAdmin webmas...@localhost
>>
>> ProxyRequests off
>>
>> Order deny,allow
>>
On Thu, Jun 10, 2010 at 7:04 PM, Tom Evans wrote:
> Then your vhost should look like this:
>
>
> ServerName site1.mydomain.com
> ServerAdmin webmas...@localhost
>
> ProxyRequests off
>
> Order deny,allow
> Allow from all
>
> ProxyPreserveHost On
> ProxyPass /m
On Thu, Jun 10, 2010 at 7:04 PM, Tom Evans wrote:
> The section is not right at all.
>
> Stop me where I get it wrong
>
> site1.mydomain.com is your 'publicly available address' and you want
> your websites on 192.168.1.10 to appear proxied on this domain.
> site1.mydomain.com/mingle/ should pro
On Thu, Jun 10, 2010 at 1:11 PM, Tapas Mishra wrote:
> Actually I have got quite confused.
> I will tell from start.
..
>
>
> ServerName site1.mydomain.com
> ServerAdmin webmas...@localhost
>
> ProxyRequests off
>
> Order deny,allow
> Allow from all
>
Actually I have got quite confused.
I will tell from start.
I am running a website.
http://site1.mydomain.com
on a pc on LAN.
There is a server which has a public IP.
I have access to modify what ever Apache file is needed.
That server does not have a DNS.
Server A
On Thu, Jun 10, 2010 at 7:43 AM, Tapas Mishra wrote:
> On Thu, Jun 10, 2010 at 4:34 PM, Eric Covener wrote:
>>>
>> Try adding the R flag on the first RewriteRule.
> Ok it did seem to do some thing.
> Actually the application is not developed by me.When some one types on LAN
> http://192.168.1.10
On Thu, Jun 10, 2010 at 4:34 PM, Eric Covener wrote:
>>
> Try adding the R flag on the first RewriteRule.
Ok it did seem to do some thing.
Actually the application is not developed by me.When some one types on LAN
http://192.168.1.10:8080
a welcome screen comes that is of mingle.
After that it a
>
> ReWriteEngine on
> ReWriteRule /application/(.*) - [L]
> RewriteRule ^/(.*) http://site1.mydomain.com:8080/$1 [P,L]
>
>
> /application gives a login screen after some one logs in /application
> is not present on the URL of client browser
> only http://site1.mydom
Hi,
I am using a backend server to serve an application which is running
on apache and another apache which is front end to users coming from
internet.
So the back end server is hidden from outside.
I want if some one types in URL
http://site1.mydomain.com/application
then they be redirected to
Eric Covener wrote, On 4/19/2010 2:59 PM:
> On Mon, Apr 19, 2010 at 5:44 PM, Glenn Gillis wrote:
>> Would any rewriting gurus out there care to speculate why the rewrite rule:
>>
>> "RewriteRule /blog http://spotlight.wordpress.com/";
>>
>> would cause the image URL:
>>
>> "> alt="what we do" w
On Mon, Apr 19, 2010 at 5:59 PM, Eric Covener wrote:
> On Mon, Apr 19, 2010 at 5:44 PM, Glenn Gillis wrote:
> > Would any rewriting gurus out there care to speculate why the rewrite
> rule:
> >
> > "RewriteRule /blog http://spotlight.wordpress.com/";
> >
> > would cause the image URL:
> >
> >
On Mon, Apr 19, 2010 at 5:44 PM, Glenn Gillis wrote:
> Would any rewriting gurus out there care to speculate why the rewrite rule:
>
> "RewriteRule /blog http://spotlight.wordpress.com/";
>
> would cause the image URL:
>
> " alt="what we do" width="500" height="125" />"
>
> to redirect to the s
Would any rewriting gurus out there care to speculate why the rewrite rule:
"RewriteRule /blog http://spotlight.wordpress.com/";
would cause the image URL:
""
to redirect to the spotlight.wordpress.com webpage?
Running Apache 2.2.9 on FreeBSD 6.x.
--
Thanks!
Glenn Gillis
Information Tech
it matchs url that NOT begin with dot ".", redirect to (part matched).html
Best regards,
Sharl.Jimh.Tsin
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for
Hi,
Basically wants to understand about the below Rewrite Rule
RewriteRule ^([^.]+)$ $1.html
Please help me understand.
Thanks and Regards,
Kaushal
-
The official User-To-User support forum of the Apache HTTP Server Project.
Just put ^(n=3)$ and it will work
On Mar 12, 2010 3:34 AM, "Francis GALIEGUE" wrote:
On Thu, Mar 11, 2010 at 16:56, Richard Schoenig
wrote:
> So here is the issue I am having now I have separate servers I am trying
to > set this rule up on ...
[...]
> RewriteCond %{QUERY_STRING} ^(n=[3]+)$
On Thu, Mar 11, 2010 at 16:56, Richard Schoenig
wrote:
> So here is the issue I am having now I have separate servers I am trying to
> set this rule up on so that if a n=1 or an n=2 it accesses server 1, and if
> an n=3 then it accesses server 2
>
[...]
> RewriteCond %{QUERY_STRING} ^(n=[3]+)$
W
On 11 March 2010 15:56, Richard Schoenig wrote:
> So here is the issue I am having now I have separate servers I am trying to
> set this rule up on so that if a n=1 or an n=2 it accesses server 1, and if
> an n=3 then it accesses server 2
>
>
>
> The rules I have setup are on server 2 I have it co
ici...@gmail.com]
>Sent: Thursday, March 11, 2010 12:32 AM
>To: users@httpd.apache.org
>Subject: Re: [us...@httpd] rewrite rule
>http://server4/perl.pl?n=1 to http://server1/perl.pl?n=1
>You can't test it on the localhost since you are redirecting some page
to i
>
> http://server4/perl.pl?n=1 to http://server1/perl.pl?n=1
>
You can't test it on the localhost since you are redirecting some page to
itself => infinite loop
Try redirecting to some imaginary domain or google.com
RewriteCond %{QUERY_STRING} ^(n=[0-9]+)$
RewriteRule ^/perl.pl$ http
On Thu, Mar 11, 2010 at 12:12 AM, Richard Schoenig
wrote:
> I am new to using mod_rewrite and have been trying to create a rule to do
> something rather simple, but keep hitting a wall. I have been trying to
> research online how to do it, but I keep finding global changes and not
> specific to w
I am new to using mod_rewrite and have been trying to create a rule to
do something rather simple, but keep hitting a wall. I have been trying
to research online how to do it, but I keep finding global changes and
not specific to what I am trying to do. Essentially I am looking to use
a rewrite r
Jai wrote:
...
It redirects to
/AgentAuthenticationService/AgentAuthenticationSoapBindingImplBean instead
of
/AgentAuthenticationService/AgentAuthenticationAndAuthorizationSoapBindingImplBean.
Is there any restriction in number of characters in rewrite rule?
I don't know, but looking at the
2009/9/15 Jai :
> We have folloeing rewrite rules in our apache configuration files.
>
> RewriteRule ^/AuthenticateService/Agent/Authenticate
> /AgentAuthenticationService/AgentAuthenticationSoapBindingImplBean [PT]
> RewriteRule ^/AuthenticateService/Agent/Authorize
> /AgentAuthenticationService/A
We have folloeing rewrite rules in our apache configuration files.
RewriteRule ^/AuthenticateService/Agent/Authenticate
/AgentAuthenticationService/AgentAuthenticationSoapBindingImplBean [PT]
RewriteRule ^/AuthenticateService/Agent/Authorize
/AgentAuthenticationService/AgencyAuthorizationSoapBindi
On Wed, Jun 10, 2009 at 8:06 AM, Singh, Sukhjeet
wrote:
> Eric,
>
> I think you are right cuz the rewrite rule which I'm using and also the
> ErrorDocument which I'm using are using the path of the files and not the
> exact URL.
>
> But while I'm able to fix the custom 403 and 404 pages, I'm not
g this vulnerability.
Sukhjeet
-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: Wednesday, June 10, 2009 5:33 PM
To: users@httpd.apache.org
Subject: Re: [us...@httpd] Rewrite Rule for hiding Destination URL ??
On Wed, Jun 10, 2009 at 5:52 AM, BipinDas-Gmail wrote:
>
On Wed, Jun 10, 2009 at 5:52 AM, BipinDas-Gmail wrote:
> I need to rewrite the url http://123.dev.com to http://123.dev.com/profile
>
> I have put the below code to my .htaccesss that successfully worked
>
> # ---
>
> rewritecond %{http_host
BipinDas-Gmail wrote:
Hello All,
I need to rewrite the url http://123.dev.com to http://123.dev.com/profile
1) Since you are rewriting everything that is "/*" to "/profile/*"
anyway, then why don't you move everything that is now under /profile,
to / ,
and be done with all the rewriting
Hello All,
I need to rewrite the url http://123.dev.com to http://123.dev.com/profile
I have put the below code to my .htaccesss that successfully worked
# ---
rewritecond %{http_host} ^widgets\.cmdn\.com$
rewritecond %{request_uri} ^/
On Fri, Jan 9, 2009 at 6:26 AM, Anders Norrbring wrote:
> Hi.
> I'm looking at a setup with 6 different ServerAlias in the same single
> VirtualHost, and I want a rewrite rule that can rewrite calls missing the
> 'www' part to add that.
>
> Looking at example pages I see that this works for a sing
But this can become tedious if you
have a large number of URLs that you need to do this for.
-Original Message-
From: Bob Ionescu [mailto:bobsie...@googlemail.com]
Sent: Friday, January 09, 2009 6:34 AM
To: users@httpd.apache.org
Subject: Re: [us...@httpd] rewrite rule ideas needed..
20
> 2009/1/9 Anders Norrbring :
> > But how can I create a setup that will simple add www to any of the
> valid
> > ServerAlias names listed in the virtual host? They shall keep the
> domain
> > name part as is, and not rewrite to one name only.
>
> Have a look at the last example of the section "C
2009/1/9 Anders Norrbring :
> But how can I create a setup that will simple add www to any of the valid
> ServerAlias names listed in the virtual host? They shall keep the domain
> name part as is, and not rewrite to one name only.
Have a look at the last example of the section "Canonical Hostnam
Hi.
I'm looking at a setup with 6 different ServerAlias in the same single
VirtualHost, and I want a rewrite rule that can rewrite calls missing the
'www' part to add that.
Looking at example pages I see that this works for a single host name:
RewriteEngine On
RewriteCond %{HTTP_HOST} !
59 matches
Mail list logo
