From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM, MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Thread: 103376,cf63aa865428ef92 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!news.glorb.com!fr.ip.ndsoftware.net!proxad.net!usenet-fr.net!news.enst.fr!melchior!cuivre.fr.eu.org!melchior.frmug.org!not-for-mail From: Marius Amado Alves Newsgroups: comp.lang.ada Subject: Re: An Index to Ada.Containers Date: Thu, 21 Apr 2005 11:54:01 +0100 Organization: Cuivre, Argent, Or Message-ID: References: <7b64bac9aa0bf3d4538773523a27d6e5@netcabo.pt> <1114066707.10019.13.camel@localhost.localdomain> <940170f9529bee39c8cc2995911ceea4@netcabo.pt> <1114079282.10019.34.camel@localhost.localdomain> NNTP-Posting-Host: lovelace.ada-france.org Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Trace: melchior.cuivre.fr.eu.org 1114080887 56718 212.85.156.195 (21 Apr 2005 10:54:47 GMT) X-Complaints-To: usenet@melchior.cuivre.fr.eu.org NNTP-Posting-Date: Thu, 21 Apr 2005 10:54:47 +0000 (UTC) Cc: comp.lang.ada@ada-france.org To: Duncan Sands Return-Path: In-Reply-To: <1114079282.10019.34.camel@localhost.localdomain> X-Mailer: Apple Mail (2.619.2) X-OriginalArrivalTime: 21 Apr 2005 10:54:04.0921 (UTC) FILETIME=[6F5EB690:01C54660] X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at ada-france.org X-BeenThere: comp.lang.ada@ada-france.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Gateway to the comp.lang.ada Usenet newsgroup" List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: g2news1.google.com comp.lang.ada:10627 Date: 2005-04-21T11:54:01+01:00 On 21 Apr 2005, at 11:28, Duncan Sands wrote: > "... You attached an ':' to the end of the URL." (Marius) > > actually, no. The colon was part of the error message, not the URL. That's not what the server error log says. It has a single entry for the malformed URL.