I'll preface this with I'm not an expert but why not just put whatever you have
in the htaccess file in your Directory section. Everything is in one place.
I don't think you need to modify httpd.conf.
If it works it's probably good.
Alain Roger wrote:
>Hi,
>
>on my local computer (localhost
yes, exactly!
omg, I'm so stupid! thanks a lot, Eric!!
-- TY
On Fri, Jan 6, 2012 at 3:55 PM, Eric Covener wrote:
> > But it seems that "SSLRequireSSL" has no effect at all. I can still
> access
> > the "DocumentRoot" using HTTP. But if I put the block out of
> the
> > block to be a separate,
> But it seems that "SSLRequireSSL" has no effect at all. I can still access
> the "DocumentRoot" using HTTP. But if I put the block out of the
> block to be a separate, independent block (not nested). It
> actually works.
>
> Could anyone tell me why?
When they're using HTTP, the config in your
Hi, all,
I have some problem about the directive "SSLRequireSSL".
I setup my SSL for and it works pretty well.
Then, I want to let Apache deny all the access when SSL is not used for the
HTTP request. In other words, I want to forbid access unless HTTP over SSL
(i.e. HTTPS) is used. According to
Hi,
on my local computer (localhost on windows 7) i installed Apache to use
Joomla.
I setup virtual host (\apache\conf\extra\httpd-vhosts.conf) and it works
great.
now for each virtual host, i would like to use a special .htaccess file, so
i added:
AccessFileName .htaccess
here is an example of
> How do I tell it to just use /tmp/list as a filesystem path?
I've never noticed, but it seems like it simply doesn't work in
per-dir. Kind of surprised and hope I am missing something.
Basically no opposite of [PT] and it always uses PT-like logic in per-dir.
Might need to establish an alias
I've got a per-directory .htaccess file. It lives in /path1.
I want to rewrite all requests for *.js to /path2/other.js.
I'm getting a 404 error. /path2/other.js is world-readable.
So far, in my testing, it seems like I can do it if I put the
RewriteRule in the section, but not in the
per-direc
Jaco Kroon wrote:
> Hi,
>
> That is a very good question indeed. I would bet that cygwin is most
> likely your best option, look for a package called patch, and you will
> need to extract the patch first with gunzip. Once on the "cygwin
> terminal" (probably some variant of bash), cd into the ba
Is there any ticket for this bug, or is it fixed internally?
I just want to check whether it's really a bug, before I start to debug for
some hours.
If it's convenient for you, I can also check the source RPM (just tell me
what should I search).
Ákos
2012. január 6. 09:34:22 dátummal Eric Cov
Hi,
I want everything for my website example.com to get redirected over
Https except for three urls
example.com -> redirect
example.com/index.php?entryPoint=one -> do not redirect
example.com/index.php?entryPoint=two-> do not redirect
example.com/index.php?entryPoint=three-> do not redirect
I
Anyway, I am more wondering if 2.2.22 is even on track to address
these issues. Or if there are patches for 2.2.X (I found trunk
patches but they only dealt with some of the CVE and didn't address
the 2.2 branch). The amount of information available for these CVEs
since sparse compared to m
Looks like a recent bug backported into your 2.2.21
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@
On 01/06/2012 10:23 AM, Szőts Ákos wrote:
No, I don't think so; ModSecurity just get triggered because something in
the error_log.
"As to the OPTIONS * request failing - make sure there are no hidden
rewrite rules or other URI mangling going on."
Thank you for the tip. Is there any (easy) way t
No, I don't think so; ModSecurity just get triggered because something in
the error_log.
"As to the OPTIONS * request failing - make sure there are no hidden
rewrite rules or other URI mangling going on."
Thank you for the tip. Is there any (easy) way to debug which rewrite rules
were applied
Hi,
That is a very good question indeed. I would bet that cygwin is most
likely your best option, look for a package called patch, and you will
need to extract the patch first with gunzip. Once on the "cygwin
terminal" (probably some variant of bash), cd into the base folder for
you httpd s
15 matches
Mail list logo