You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Nick Rudnick <jo...@t-online.de> on 2011/02/11 23:08:08 UTC
[users@httpd] SSH authentication: Multiple authentication dialog windows popping
up
Dear all,
after googling some time without success, here a question:
Thinking to have followed the instructions so far, I got SSL
authentication successful with one exception:
At the first time authenticating, the user gets multiple authentication
request dialog windows (for each requested file, e.g. *.html, *.css
etc.) popping up. It seems to suffice to fill out the first dialog and
close the others, but still this is annoying behaviour I didn't
experience at other applications.
An idea seems to reduce the number of files to authenticate to 1 at
entering, but I guess the might be a more elegant way -- did anybody
encounter similar problems and, possibly, find a nice solution?
Thank you very much in advance,
Nick
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] database expires and kills website
Posted by Norman Fournier <no...@normanfournier.com>.
On 2011-02-15, at 9:52 AM, Tom Evans wrote:
> On Tue, Feb 15, 2011 at 4:38 PM, Norman Fournier
> <no...@normanfournier.com> wrote:
>> Krist
>>
>> Hello,
>> I thought it was all part and parcel of the Apache configuration. The
>> relevant part of the .db file looks like this:
>> $ORIGIN .
>> $TTL 14400 ; 4 hours
>> e4edmonton.com IN SOA
>> ns1.normanfournier.com. postmaster.e4edmonton.com. (
>> 2010020305 ; serial
>> 21600 ; refresh (6 hours)
>> 900 ; retry (15 minutes)
>> 604800 ; expire (1 week)
>> 43200 ; minimum (12 hours)
>> )
>> NS ns1.normanfournier.com.
>> NS ns2.normanfournier.com.
>> --snip--
>> All of the website I host use this same type of file but they stay
>> permanently online.
>> Are there problems with the version of Apache I am using? I would hate to
>> break it by upgrading. I have had bad experiences after upgrading software
>> and applications that will not run on a later version, so I am a little gun
>> shy.
>> Norman
>
> That is a BIND zone file. BIND has nothing to do with apache. See here
> for support for BIND:
>
> http://www.isc.org/software/bind
>
> FYI apache 1.3 is considered seriously old. You should investigate
> moving to apache 2.0 or 2.2 immediately.
>
> Cheers
>
> Tom
Thanks for the URL Tom. I'll have a look there.
Norman
---
http://www.normanfournier.com
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] database expires and kills website
Posted by Tom Evans <te...@googlemail.com>.
On Tue, Feb 15, 2011 at 4:38 PM, Norman Fournier
<no...@normanfournier.com> wrote:
> Krist
>
> Hello,
> I thought it was all part and parcel of the Apache configuration. The
> relevant part of the .db file looks like this:
> $ORIGIN .
> $TTL 14400 ; 4 hours
> e4edmonton.com IN SOA
> ns1.normanfournier.com. postmaster.e4edmonton.com. (
> 2010020305 ; serial
> 21600 ; refresh (6 hours)
> 900 ; retry (15 minutes)
> 604800 ; expire (1 week)
> 43200 ; minimum (12 hours)
> )
> NS ns1.normanfournier.com.
> NS ns2.normanfournier.com.
> --snip--
> All of the website I host use this same type of file but they stay
> permanently online.
> Are there problems with the version of Apache I am using? I would hate to
> break it by upgrading. I have had bad experiences after upgrading software
> and applications that will not run on a later version, so I am a little gun
> shy.
> Norman
That is a BIND zone file. BIND has nothing to do with apache. See here
for support for BIND:
http://www.isc.org/software/bind
FYI apache 1.3 is considered seriously old. You should investigate
moving to apache 2.0 or 2.2 immediately.
Cheers
Tom
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] database expires and kills website
Posted by Norman Fournier <no...@normanfournier.com>.
On 2011-02-15, at 6:45 AM, Krist van Besien wrote:
> On Mon, Feb 14, 2011 at 4:54 PM, Norman Fournier
> <no...@normanfournier.com> wrote:
>
>> I have a website running with an expiry date set for 1 week in the database file. Once the .db file expires the site goes offline. I then have increment the serial number, to grep for "named" and -HUP the process to bring the site online again.
>>
>> All of my other sites use the same configuration of .conf and .db files and stay online, except this particular URL. As a matter of fact, I copied a successful .conf and .db file and edited them to create them. The other sites have a .db expiry of 1 week also.
>>
>> Where would you suggest I begin to look for the error or do you have any ideas what could be the cause of this behaviour.
>
> I have no idea what you mean with an expiry date on a database file.
> Could you be more specific? Apache itself does not use db files. Some
> website you have installed might, but you are not telling us enough...
>
>> I am running Apache 1.3.41 on OSX 10.4.11
>
> Why are you using such an old version of apache?
>
> Krist
Hello,
I thought it was all part and parcel of the Apache configuration. The relevant part of the .db file looks like this:
$ORIGIN .
$TTL 14400 ; 4 hours
e4edmonton.com IN SOA ns1.normanfournier.com. postmaster.e4edmonton.com. (
2010020305 ; serial
21600 ; refresh (6 hours)
900 ; retry (15 minutes)
604800 ; expire (1 week)
43200 ; minimum (12 hours)
)
NS ns1.normanfournier.com.
NS ns2.normanfournier.com.
--snip--
All of the website I host use this same type of file but they stay permanently online.
Are there problems with the version of Apache I am using? I would hate to break it by upgrading. I have had bad experiences after upgrading software and applications that will not run on a later version, so I am a little gun shy.
Norman
---
http://www.normanfournier.com
Re: [users@httpd] database expires and kills website
Posted by Krist van Besien <kr...@gmail.com>.
On Mon, Feb 14, 2011 at 4:54 PM, Norman Fournier
<no...@normanfournier.com> wrote:
> I have a website running with an expiry date set for 1 week in the database file. Once the .db file expires the site goes offline. I then have increment the serial number, to grep for "named" and -HUP the process to bring the site online again.
>
> All of my other sites use the same configuration of .conf and .db files and stay online, except this particular URL. As a matter of fact, I copied a successful .conf and .db file and edited them to create them. The other sites have a .db expiry of 1 week also.
>
> Where would you suggest I begin to look for the error or do you have any ideas what could be the cause of this behaviour.
I have no idea what you mean with an expiry date on a database file.
Could you be more specific? Apache itself does not use db files. Some
website you have installed might, but you are not telling us enough...
> I am running Apache 1.3.41 on OSX 10.4.11
Why are you using such an old version of apache?
Krist
--
krist.vanbesien@gmail.com
krist@vanbesien.org
Bremgarten b. Bern, Switzerland
--
A: It reverses the normal flow of conversation.
Q: What's wrong with top-posting?
A: Top-posting.
Q: What's the biggest scourge on plain text email discussions?
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
[users@httpd] database expires and kills website
Posted by Norman Fournier <no...@normanfournier.com>.
Hello,
A newbie question:
I have a website running with an expiry date set for 1 week in the database file. Once the .db file expires the site goes offline. I then have increment the serial number, to grep for "named" and -HUP the process to bring the site online again.
All of my other sites use the same configuration of .conf and .db files and stay online, except this particular URL. As a matter of fact, I copied a successful .conf and .db file and edited them to create them. The other sites have a .db expiry of 1 week also.
Where would you suggest I begin to look for the error or do you have any ideas what could be the cause of this behaviour.
I am running Apache 1.3.41 on OSX 10.4.11
Thank you
Norman
---
http://www.normanfournier.com
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SSH authentication: Multiple authentication dialog
windows popping up
Posted by Ben Timby <bt...@gmail.com>.
Nick, this does not sound right to me. Here is why:
If your main HTML was protected by login, the user would be prompted
to authenticate themselves before receiving the HTML. This would keep
the browser from making further requests until authentication
occurred.
It sounds like in your situation, that main HTML is NOT protected,
thus the browser receives it, parses it and then makes requests for
additional resources, at which point authentication is triggered for
the multiple resources the browser fetches in parallel.
You need to ensure that the initial content triggers authentication,
so that the subsequent requests can reuse the authentication
information.
If you look in your log files, likely you will see a 200 reply for the
page, followed by many 401 replies for the resources. You should see a
401 for the page followed by a 200 for the page followed by 200's for
the resources.
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org