On Tue, 04 Oct 2005 16:44, Boyle Owen wrote:
>
> Just to clear up some apparent confusion on this thread: I think the
> point everyone is missing is that an SSL-encrypted website uses a
> *different protocol* than plain old HTTP. Instead of thinking of SSL as
> some sort of add-on (like mod_perl) t
Boyle Owen wrote:
Just to clear up some apparent confusion on this thread: I think the point everyone is missing is
that an SSL-encrypted website uses a *different protocol* than plain old HTTP. Instead of thinking
of SSL as some sort of add-on (like mod_perl) to a "normal" website, look caref
> -Original Message-
> From: Brian [mailto:[EMAIL PROTECTED]
> Sent: Montag, 3. Oktober 2005 18:45
> To: users@httpd.apache.org
> Subject: [EMAIL PROTECTED] Cluster Question
>
>
> Before I begin, let me make it clear I'm new to apache
> and open to suggestion/ direction to references.
> T
> -Original Message-
> From: Axel-Stéphane SMORGRAV
>
> If you are planning on serving both SSL and non-SSL
> connections, then yes, a separate virtual host is necessary
> for one of the two.
>
> The fact is that the SSLEngine directive is only valid in a
> server or virtual host conte
On Tue, 04 Oct 2005 16:07, Axel-Stéphane SMORGRAV wrote:
> If you are planning on serving both SSL and non-SSL connections, then
> yes, a separate virtual host is necessary for one of the two.
>
> The fact is that the SSLEngine directive is only valid in a server or
> virtual host context. I do not
On Mon, Oct 03, 2005 at 03:00:37PM +0200, Vincent Blondel wrote:
>
> My society needs a package containing apache that must meet next requirements
> :
>
> - all data , software and configuration must be isolated in /opt/apache
> - the package needs to run on FreeBSD
ports(7) about PREFIX
> - /o
If you are planning on serving both SSL and non-SSL connections, then yes, a
separate virtual host is necessary for one of the two.
The fact is that the SSLEngine directive is only valid in a server or virtual
host context. I do not know the reason for that, but I am sure there is one.
The most
On Tue, 04 Oct 2005 10:36, Paul Annesley wrote:
> I believe the error you are getting is often caused by trying to serve
> plain HTTP on port 443, instead of HTTPS which the browser is
> expecting..
That's a reasonable suggestion. I have not set any parameters which tell it
what port serves which
No it is not required to have a separate virtual host,
at least not for Apache itself. I am running V2.054
http and https on FreeBSD V5.3 with no problem.
BZAG
=
--- Andrew Clarke <[EMAIL PROTECTED]> wrote:
>
> SuSE 9.3 hosting Apache 2.0.53 (the build from SuSE
>
I believe the error you are getting is often caused by trying to serve
plain HTTP on port 443, instead of HTTPS which the browser is
expecting..
Regards,
Paul
On 10/4/05, Andrew Clarke <[EMAIL PROTECTED]> wrote:
>
>
> On a closely related topic, I eventually reached the point of creating a
> self
SuSE 9.3 hosting Apache 2.0.53 (the build from SuSE installs) and Firefox
1.0.6 for a self-contained server and workstation on a laptop.
I'm working on getting https working for the first time, and keep reading
hints that it's usual to make another virtual host to carry the SSL. Is
this requir
Or use the commands:
net start apache2
and
net stop apache2
Teddy
- Original Message -
From: "Joshua Kogut" <[EMAIL PROTECTED]>
To: ; <[EMAIL PROTECTED]>
Sent: Monday, October 03, 2005 22:15 PM
Subject: Re: [EMAIL PROTECTED] Re: starting the daemon from a command prompt
Or just add t
Whenever developing your site, I recommend testing on your local
server, then disabling your browsers cache. Then you will never see a
previous version of the ste that you are working on, and will eliminate
any cache systems between you and the server.On 10/3/05, Joshua Slive <[EMAIL PROTECTED]> wr
Or just add the Apache bin folder to your include path by going to your
system properties window [windows key + pause/break] in the
advanced tab, in environment variables. Doulbe click the [path] line,
and then add a semicolon and then your apache directory, after you are
done with that, and resta
On 10/3/05, Ryan McDonald <[EMAIL PROTECTED]> wrote:
> Hello everyone,
>
> When a browser makes a conditional request to see if a resource it has
> cached has changed, and that resource has not changed will that request
> be logged by apache and show the proper response code of 304?
Yes.
>
> I am
Well, running Apache in WinXP isn't as easy in say the OS of choice,
(any version of *nix), but I have recently devoted myself to
contributing to the WinXP aspect of the documentation so that it
doesn't have to be so hard. To answer you question, First, make sure
your listen port is set to the defa
I get this error often when I misconfigure something in Apache http.
The first thing you want to do is to disable any changes that you have
recently made, then start Apache. If it works, then you know the
specific module that is giving you problems. Look over your
configuration for that module and
Hello everyone,
When a browser makes a conditional request to see if a resource it has
cached has changed, and that resource has not changed will that request
be logged by apache and show the proper response code of 304?
I am trying to figure out why a browser is not receiving updated js
fil
Before I begin, let me make it clear I'm new to apache
and open to suggestion/ direction to references.
Thanks in advance.
We have an IBM cluster at work.
It is set up as a typical cluster. Box A and Box B
with shared space.
It is supposed to be our HTTP server. So virtual Box C
is the entry poin
I did not mention any LockFile directive in httpd.conf, so I defined it and it
works now :)
Thanks a lot
Vincent
> Check your AcceptMutex setting. You are probably using the flock or fcntl
> method and the lock file is owned by root. Therefore Apache
> is now unable to lock the resource. Unles
http://www.faqs.org/docs/Linux-HOWTO/Apache-WebDAV-LDAP-HOWTO.html#AEN488
Hope this helps.
./Bhavin
On 10/3/05, John <[EMAIL PROTECTED]> wrote:
Hi allI have encrypted the private key and every time that i star apache2.0.54 it requires the password.
How could i overcome that obstacle?Thanks in
Hi all
I have encrypted the private key and every time that i star apache
2.0.54 it requires the password.
How could i overcome that obstacle?
Thanks in advance
-
The official User-To-User support forum of the Apache HTTP Ser
First of all, if you're using Apache bundled with some software distribution, make sure that they don't use more than one configuration file. Look for "Include" directives in the apache2.conf file and other Apache configuration files in the configuration directory. The DocumentRoot directive may
Hi,
I am using apache2 presently default document root directory is /var/www/.If i want to change this to /home/www/.How do i do this and where i can change.Present apache2.conf file is not showing the default root directory .
Thanks for your help
Best Regards
Yahoo! for Good
Click here t
Using Suse 9.3, Apache 2 and hosting two sites currently, let's say X and Y.
Absolute paths and document roots are specified in vhost files as /srv/www/X
and /srv/www/Y.
I have a ~400-line entry .htaccess file that has a lot of setenvifcase's in
it, to block a lot of crawlers, indexers, etc., even
I'have installed Apache 2.0 on fedora
core 3
I'm using apache as reverse proxy and
it works well.
I type the URL :
http://myreverseproxy:8081
and I get a login page
I type login/password and apache authenticate
me in MS Active Directory.
So i cat get the login page of a web
application (on anot
I "chmod 777" ( just for the test) all "run" and "log" directories so that I
am sure all *.pid *.log and all running stuffs can be
created but what is suprising me is that the log file does not mention this
filename.
Even when I truss the httpd process I get thousands of lines corresponding to
Check your AcceptMutex setting. You are probably using the flock or fcntl
method and the lock file is owned by root. Therefore Apache is now unable to
lock the resource. Unless you have explicitly specified LockFile, you should
find the lock file under SERVER_ROOT/logs/accept.lock
-ascs
-O
Vincent,
Apache wants to create a file httpd.pid (usually in the logs
directory) - check entry from httpd.conf. This directory is often
owned by root, which means user apache cannot wite the file at
startup.
rgds
-
The offi
This is not my case because "Listen" is configured with port 8080 to bypass
this problem and when I run it with root it is correctly
listening on port 8080.
> Vincent Blondel wrote:
>> Hello all,
>>
>> My society needs a package containing apache that must meet next
>> requirements :
>>
>> - al
Vincent Blondel wrote:
Hello all,
My society needs a package containing apache that must meet next requirements :
- all data , software and configuration must be isolated in /opt/apache
- the package needs to run on FreeBSD
- /opt/apache ( and all files in it ) must be owned by user:group apach
Hello all,
My society needs a package containing apache that must meet next requirements :
- all data , software and configuration must be isolated in /opt/apache
- the package needs to run on FreeBSD
- /opt/apache ( and all files in it ) must be owned by user:group apache:apache
<--> 0755
- ht
As far as I can tell, in Apache versions 2.0.49 and prior the default Mutex
type (at least for AcceptMutex) was pthread. It then changed to fcntl around
Apache 2.0.50 leading me to post the following
http://issues.eu.apache.org/bugzilla/show_bug.cgi?id=32325 issue, and
explicitly set both mutex
33 matches
Mail list logo
