Hello!
That's not an Apache issue at all it is basic networking
configuration at the OS level.
What you need is to get a good book on Unix system administration,
hopefully one aimed at your particular OS.
Dragon
What I from start didn't know I wanted to change, is as you say
networkin
EWD wrote:
> Florian,
>
> I had sent this email from Nabble and after about 30 minutes I came back to
> see what's up and I saw that my email is not sent yet and Nabble offered me
> to resend it.
you should check the list to see if it was posted yet before sending it
again.
--
I think you're right.
On Tue, December 18, 2007 17:53, EWD wrote:
>
> Florian,
>
> I had sent this email from Nabble and after about 30 minutes I came back to
> see what's up and I saw that my email is not sent yet and Nabble offered me
> to resend it. And then most probably Nabble has been able t
How would I configure/compile Apache 2.2/mod_dav to use the old dbm format for
property database files, as opposed to using the sdbm/gdbm/db formats?
I already compiled and installed apr-util with --with-db=dbm, but mod_dav
continues to use SDBM/GDBM.
-RG
--
On Dec 18, 2007 11:50 AM, Ryan Klein <[EMAIL PROTECTED]> wrote:
> I am having an issue redirecting a domain, twice? The general layout is
> I have www.domain.com and domain.com redirect to https://domain.com, the
> problem I am having is how to have https://www.domain.com redirect to
> https://doma
Florian,
I had sent this email from Nabble and after about 30 minutes I came back to
see what's up and I saw that my email is not sent yet and Nabble offered me
to resend it. And then most probably Nabble has been able to send both
messages to Apache. Apologies for that, but at the same time, you
I am having an issue redirecting a domain, twice? The general layout is
I have www.domain.com and domain.com redirect to https://domain.com, the
problem I am having is how to have https://www.domain.com redirect to
https://domain.com without giving a certificate error saying the
certificate is
No need for reverse proxying. No need for linking. No need for
sub-domain. No need for additional IP addresses.
1. Have whoever manages your domain ewd.net create a DNS CNAME record
app.ewd.net IN CNAME www.ewd.net
2. Read up on name-based virtual hosting at
http://httpd.apache.org/docs/2
Hans Tovetjärn wrote:
Hello!
Thank you, it worked! It does give me the
warning, but that is perhaps not a big issue.
This is really a jungle to me right now though,
in what part of the Apache documentation can I read more about this?
In that case there is maybe another way around it.
In /
Hi Edsger,
first, simply resending your email is not cool. Resending it on the same day
is close to being annoying. I already read your first email, I think many
others did that too. Please avoid that in the future.
What you want, is called a subdomain, you need your provider to arrange that.
Af
On Dec 18, 2007 9:04 AM, Asrai khn <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 18, 2007 2:30 AM, Joshua Slive <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > No, if you put it outside of any it should log for all
> > virtual hosts.
> >
> >
> >
> >
> >
> >
>
> Hi Joshua
>
> Thanks for all the tips, i
On Dec 18, 2007 2:30 AM, Joshua Slive <[EMAIL PROTECTED]> wrote:
>
> No, if you put it outside of any it should log for all
> virtual hosts.
>
>
>
Hi Joshua
Thanks for all the tips, i have enabled mod_log_forensic on our shared web
server and and also get the 'check_forensic' script.
sudo /usr/
I do not know whether there is anything about this in the doc.
Looking at the source code (server/util.c and server/vhost.c) I figured out
that Apache at some point tries to resolve the address associated with the host
name on which it is running. Normally this does not pose any problem because
Hello!
Thank you, it worked! It does give me the warning, but that is
perhaps not a big issue. This is really a jungle to me right now
though, in what part of the Apache documentation can I read more
about this?
In that case there is maybe another way around it.
In /etc/hosts, change th
In that case there is maybe another way around it.
In /etc/hosts, change the line
127.0.0.1 localhost
into
127.0.0.1 localhost laptop
That should keep Apache happy.
-ascs
-Message d'origine-
De : Hans Tovetjärn [mailto:[EMAIL PROTECTED]
Envoyé : mardi 18 décembre 2007
> -Original Message-
> From: Artem Kuchin [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 13, 2007 11:32 AM
> To: users@httpd.apache.org
> Subject: [EMAIL PROTECTED] How to resist user click abuse in apache?
>
> Here is the situation. Heavy db driven site takes about 1-1.5 second
> t
Hello,
there is no such line in /etc/hosts, unfortunately:
"##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost "
My IP is recie
> -Original Message-
> From: goommy [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 17, 2007 9:41 AM
> To: apache??
> Subject: [EMAIL PROTECTED] Why access_log so large?
>
> hi，list！
>
> My server use 1.3 and work well all the time.
> Recently，i upate 1.3 to 2.2 with the configur
18 matches
Mail list logo
