Apache can't interpret the following link : link
href=../../chorus-theme/css/main.css@browserId=firefoxt=1344590189623
rel=stylesheet type=text/css /
because of the @browserId=firefoxt=1344590189623 after main.css
but when I open the html file directly in the browser it works, the style
is
Shouln't that be :
../../chorus-theme/css/main.css?browserId=firefoxt=1344590189623
First non-url part is after ?, other parts seperated by
Pretty sure @ has special meaning in a url..
On 17/08/2012, at 2:03 PM, Nicolas Maujean nmauj...@gmail.com wrote:
Hi All,
a simple mod_rewrite rules
RewriteEngine On
RewriteCond /home/docroot/test/$1 -f
RewriteRule ^(.+).test$ /test/$1 [L]
http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewritecond
in apache 2.2.x this works in vhost and .htaccess context, in apache
2.4.2 in vhost context $1 in
No it is not the problem
I have resolved the problems, need to put
text/css css?browserId=firefoxt=1344590189623 in the mime.type
file1344590189623
another solution is to rename
main.css?browserId=firefoxt=1344590189623 in
main.css?browserId=firefoxt=1344590189623.css
On Fri, Aug 17, 2012 at
Im really surprised your RewriteCond worked at all in any Apache version as
it doesn't make sense to me. The $1 at the end has a meaning of variable
which in your case has a value of ... what? Maybe if you tell us whar r you
trying to do someone can help you.
On Aug 17, 2012 8:01 PM, Lazy
2012/8/17 Igor Cicimov icici...@gmail.com:
Im really surprised your RewriteCond worked at all in any Apache version as
it doesn't make sense to me. The $1 at the end has a meaning of variable
which in your case has a value of ... what? Maybe if you tell us whar r you
trying to do someone can
please read the docs,
RewriteRule backreferences: These are backreferences of the form $N (0
= N = 9).
You should read the docs, too. The keyword for you is: scope. You
cannot backreference outside the actual rewrite rule, and the
RewriteCond (i.e. the TRIGGER) is bogus at best, because
It is oposite as far as i know. You use the variables of a patern match
from RewrieCond in RewriteRule. Hence the order of the statements,
RewriteRule always comes after ReweiteCond and never the other way around.
But if you say so ...
On Aug 17, 2012 8:41 PM, Lazy lazy...@gmail.com wrote:
On Fri, Aug 17, 2012 at 6:01 AM, Lazy lazy...@gmail.com wrote:
Hi All,
a simple mod_rewrite rules
RewriteEngine On
RewriteCond /home/docroot/test/$1 -f
RewriteRule ^(.+).test$ /test/$1 [L]
http://httpd.apache.org/docs/2.4/mod/mod_rewrite.html#rewritecond
in apache 2.2.x this works in
2012/8/17 Eric Covener cove...@gmail.com:
On Fri, Aug 17, 2012 at 6:01 AM, Lazy lazy...@gmail.com wrote:
Hi All,
a simple mod_rewrite rules
RewriteEngine On
RewriteCond /home/docroot/test/$1 -f
RewriteRule ^(.+).test$ /test/$1 [L]
What's the canonical way to redirect the following?
http://host/xyz[/abc]
to
http://xyz.host/[abc]
The following works
RedirectMatch ^xyz(.*) http://xyz.host$1
but suffers from the problem that
http://host/xyz123
is redirected to
http://xyz.host123
which is not intended.
I suppose one way
The following works
RedirectMatch ^xyz(.*) http://xyz.host$1
but suffers from the problem that
http://host/xyz123
maybe RedirectMatch ^xyz(/.*)? http://xyz.host$1
-
To unsubscribe, e-mail:
On 17 August 2012 15:02, Eric Covener cove...@gmail.com wrote:
The following works
RedirectMatch ^xyz(.*) http://xyz.host$1
but suffers from the problem that
http://host/xyz123
maybe RedirectMatch ^xyz(/.*)? http://xyz.host$1
That won't match
http://host/xyz
which should redirect to
maybe RedirectMatch ^xyz(/.*)? http://xyz.host$1
That won't match
http://host/xyz
question mark was part of the regex not punctuation, but not sure the
redirect w/o trailing slash is okay.
rejiggered to always have the trailing slash:
RedirectMatch ^xyz/?(.*) http://xyz.host/$1
On 17 August 2012 15:30, Eric Covener cove...@gmail.com wrote:
maybe RedirectMatch ^xyz(/.*)? http://xyz.host$1
That won't match
http://host/xyz
question mark was part of the regex not punctuation,
Very sorry, my bad, I should have read more carefully.
Your suggestion will work fine.
On 17 August 2012 15:58, sebb seb...@gmail.com wrote:
On 17 August 2012 15:30, Eric Covener cove...@gmail.com wrote:
maybe RedirectMatch ^xyz(/.*)? http://xyz.host$1
That won't match
http://host/xyz
question mark was part of the regex not punctuation,
Very sorry, my bad, I should have
Hi List,
Some days back I came across a very weired problem, and I am not able
to figure out. The security scanners scanned one of our public facing
website and they said that webserver is vulnerable to HTTP methods or
may be webdav is enabled. I looked around the code and couln't find
anything.
Although I don't know for sure, I'm guessing it's because
TRACE is enabled. Some brain-dead security audits consider
allowing TRACE to be a security issue (although it's
not)...
Check out http://httpd.apache.org/docs/2.4/mod/core.html#traceenable
and give your security scanners a whack with a
On 18/08/2012, at 6:46 AM, Denis BUCHER dbuche...@hsolutions.ch wrote:
Dear all,
That's an unbelievable issue but we have single apache process that takes 5
GB of memory ! And it doesn't happens always with the same URLs, it's
unpredictable and we don't understand why it is happening at
19 matches
Mail list logo
