2009/7/16 Nedim Ozan Tekin :
> What might be the problems? Do you have any idea?
1) Read this: http://catb.org/esr/faqs/smart-questions.html
2) Once you've read this come back.
3) Don't hijack an existing thread, start a new one.
Krist
--
krist.vanbes...@gmail.com
kr...@vanbesien.org
Bremgart
Hello,
there is a problem with apache bundled with xampp
(xampp-win32-1.7.1-installer.exe).
I could track the problem to a trivial preg_match command in php, which runs
perfectly on the command line, but not from the server.
The help on the net via a google search was pretty confusing.
I tried s
I'm using mod_perl to serve "mason" pages.
SetHandler perl-script
PerlHandler HTML::Mason::ApacheHandler
AddType text/html mhtml
AddType text/html comp
AddHandler perl-script mhtml comp
If I load *localhost/codebank/index.html*, there is no problem.
However, if I try to
ML wrote:
Hi Tom,
Say I have a directory of files that contain my MySQL connection
information, queries, etc, etc.
How do I prevent people from browsing the directory but allow the
files to still be used when I include them in a page. Say to connect
to MySQL.
Don't ever put them inside your
If a client requests an XHTML file, it says to do normal
content-negotiation. If the client's HTTP Accept header says they like
text/html more, send them that. If it says they like application/xhtml+xml
more, send them that.
Fine. I have even done that successfully with two different files.
Ex
I've never even saw, an example of 2 certs for 2 domains in same VH
Show me httpd.conf syntax
> You need two certs. www.domain.com and domain.com.
>
> Redirect won't work in this case because it is done at the HTTP layer
> and the SSL handshake occurs before the GET request.
>
>
> --
> Aaro
You can not, as SSL mismatch error is trigered for one in FF for example
and all other major browsers
- Original Message -
From: "Jonas Eckerman"
To: users@httpd.apache.org
Date: Thu, 16 Jul 2009 15:10:25 +0200
Subject: Re: [us...@httpd] SSL cert for alias too
> > SSL cert for each, as
Igor...
You have 2 SAME rewrite rules!
Now I will translate what they mean:
IF page is requested on NON-SSL port 80 THEN rewrite url to SSL version of
it, with www..., --> redir 301, last(stop rewriting)
NOW, do you understand that second rewrite block inside will NEVER get executed.
So delet
dar...@chaosreigns.com wrote:
If a client requests an XHTML file, it says to do normal
content-negotiation.
No, if a client asks for the URL "/abc/file.html", it wants the resource
corresponding to that URL.
If the client's HTTP Accept header says they like
text/html more, send them that.
So it's not possible to serve one file with two different Content-Types,
and you think that is as it should be?
Did you read the part about why XHTML should be served to some clients as
text/html, and others as application/xhtml+xml?
application/xhtml+xml is the correct Content-Type for xhtml. S
rank1see...@gmail.com wrote:
>> Use one cert issued for both hosts.
You can not, as SSL mismatch error is trigered for one in FF for example
and all other major browsers
Not when I test with FF or IE. For example, the following three
hostnames (on three vhosts) uses the same certificate (wit
dar...@chaosreigns.com wrote:
So it's not possible to serve one file with two different Content-Types,
and you think that is as it should be?
Yes, because it would be very confusing otherwise.
But it is not what I think that counts; what counts is the HTTP RFC.
Did you read the part about wh
I moved this bit to the top because I think it makes everything else
irrelevant:
> Note however that old browsers who do not understand the type
> "application/xhtml+xml", are *really* old.
>
> Note also that no matter what the server sends as Content-Type header,
> if the browser is IE, it wi
13 matches
Mail list logo
