On Wed, 23 Oct 2002, Frederic DONNAT wrote:
A few weeks ago, i see a cvs commit about this on mod-ssl mailing list.
But i see that apache-2.0.x have not been updated.
Good that you noticed this ! Thoug there are many more experts on the
mod-ssl mailing list; this list can propably help you
William A. Rowe, Jr. [EMAIL PROTECTED] writes:
At 07:04 PM 10/25/2002, Jeff Trawick wrote:
Chandragupt [EMAIL PROTECTED] writes:
Hi,
We have developed a BioInformatics Web based Application using
CGIC , Linux and Apache as the webserver. We are using MySQL
database for data
William A. Rowe, Jr. wrote:
At 07:44 PM 10/25/2002, you wrote:
[ Simply trying again; or according to Jeff: nag, nag, nag ;-) ]
If you use the body feature in type map files, the MIME-headers
currently are set dependant on what (mostly) type_checker says about the
type map file.
The attached
http://httpd.apache.org/download.html
I believe this is better than the current circumstances because it is
clearer for the users, and it better enables us to direct people to the
mirrors for the download and the main site for the signatures.
I've never particularly like the
Joshua Slive wrote:
http://httpd.apache.org/download.html
I believe this is better than the current circumstances because it is
clearer for the users, and it better enables us to direct people to the
mirrors for the download and the main site for the signatures.
I've never particularly like
Erik Abele wrote:
+1. great idea, but I think the mirror sites should be mentioned more
than only once. Perhaps an extra paragraph like the following would help:
If you look at the actual links, you'll see I'm pretty much forcing
people to download from the mirrors. I provide direct links
Joshua Slive wrote:
Erik Abele wrote:
+1. great idea, but I think the mirror sites should be mentioned more
than only once. Perhaps an extra paragraph like the following would help:
If you look at the actual links, you'll see I'm pretty much forcing
people to download from the mirrors. I
Erik Abele wrote:
+1. great idea, but I think the mirror sites should be mentioned more
than only once.
Agreed, it's one of those things I hate most of SourceForge... I _always_
screw up, copy the link from my browser to my terminal on the wget command
line parameter, and end up with a few-kb
Pier Fumagalli wrote:
I'd say that it should be more visible that the link is an HTML rather
than
a TARball... Something like Click here to find out where you can download
HTTPD-2.0.43.tar.gz from...
Ewww... Ugly. I'm open to suggestions on improving the transparency,
but I don't like that
On 27/10/02 0:04, Joshua Slive [EMAIL PROTECTED] wrote:
Pier Fumagalli wrote:
I'd say that it should be more visible that the link is an HTML rather
than
a TARball... Something like Click here to find out where you can download
HTTPD-2.0.43.tar.gz from...
Ewww... Ugly. I'm open to
--On Sunday, October 27, 2002 12:30 AM +0100 Pier Fumagalli
[EMAIL PROTECTED] wrote:
Ok, as long as it's clear! :-) I'm very dumb, but I know other
people smarter than me who also have the same problem with
SourceForge... You simply forget! :-)
Well, I agree with Pier. I'm an idiot, too. I
On 27/10/02 0:54, David Burry [EMAIL PROTECTED] wrote:
I agree that a link on a tar.gz (etc) filename is a lot more intuitive if
it serves an actual tar.gz file... What about a script that randomly
redirects to an actual mirrored file? I realize it may be necessary to
monitor all mirrors to
Justin Erenkrantz wrote:
Well, I agree with Pier. I'm an idiot, too. I absolutely can't stand
SourceForge's mirroring system (which is essentially what that page is
moving us to). It tells me that I'm downloading a file, but when I try
to download it by hitting the link, I get an HTML file
Pier Fumagalli wrote:
On 27/10/02 0:54, David Burry wrote:
I agree that a link on a tar.gz (etc) filename is a lot more
intuitive if
it serves an actual tar.gz file... What about a script that randomly
redirects to an actual mirrored file? I realize it may be necessary to
monitor all
--On Sunday, October 27, 2002 12:30 AM +0100 Pier Fumagalli
[EMAIL PROTECTED] wrote:
Ok, as long as it's clear! :-) I'm very dumb, but I know other
people smarter than me who also have the same problem with
SourceForge... You simply forget! :-)
Well, I agree with Pier. I'm an idiot,
Excellent little utility... however closer network-wise is often
significantly different than closer geographically, for instance California
is likely a lot closer to Peru than Chile is (as an extreme example), if you
go by the packets fly instead of by the crow flies... Also when a closer
David Burry wrote:
Excellent little utility... however closer network-wise is often
significantly different than closer geographically,
Well, yeah, but that's what Akamai and the like get the big bucks for.
Sorry, we are really off-topic for dev@httpd. It might be slightly
closer on [EMAIL
Joshua Slive [mailto:joshua;slive.ca] wrote:
Pier Fumagalli wrote:
I looked into it back in the days, but the only way would
be to go down to
RIPE (IANA in the US) to see where that IP is coming from,
doing some
weirdo
WHOIS parsing and stuff... _WAY_ overkilling... Anyhow this
Jeroen Massar wrote:
A easy fix for the Sourceforge syndrome would be :
Interesting idea. I'm leaning towards just doing something like a
href=...Mirrors of httpd-.../a, which would be ugly, but clear.
Joshua.
FWIW, somehow this patch breaks Win32 with APR_HAVE_IPV6.
The Apache service named reported the following error:
[Sat Oct 26 22:45:29 2002] [crit] (OS 11001)No such host is known. :
alloc_listener: failed to set up sockaddr for :: .
No time to debug now... a dozen overdue assignments.
20 matches
Mail list logo