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
-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
to load
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
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
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 VirtualHost it should log for all
virtual hosts.
Hi Joshua
Thanks for all the tips, i have enabled
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.
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
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
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
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,
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
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
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 to
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
14 matches
Mail list logo