Return-Path: Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 37593 invoked by uid 500); 29 Apr 2002 08:02:25 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 37582 invoked from network); 29 Apr 2002 08:02:25 -0000 Received: from dsl-212-23-23-156.zen.co.uk (HELO lemonlainey.com) (212.23.23.156) by daedalus.apache.org with SMTP; 29 Apr 2002 08:02:25 -0000 Received: from cscm1xn8ksljgv by lemonlainey.com with SMTP (MDaemon.PRO.v5.0.5.R) for ; Mon, 29 Apr 2002 09:02:25 +0100 Message-ID: <003c01c1ef54$38890640$3281b2d5@iii.co.uk> Reply-To: "Kevin Smith" From: "Kevin Smith" To: Subject: Fragmented Headers Date: Mon, 29 Apr 2002 09:02:27 +0100 Organization: Netsmith Limited MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0039_01C1EF5C.95F4E990" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Lookup-Warning: reverse lookup on original sender failed X-Return-Path: kevin@netsmith.ltd.uk X-MDaemon-Deliver-To: users@httpd.apache.org X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------=_NextPart_000_0039_01C1EF5C.95F4E990 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, Does anyone know about fragmented Apache headers and what "might" cause = them? I've been informed that the further the customer is away = (geographically) the more fragmented the headers get to an extent where = the page is not served? I do not have any experience with Apache headers and their = fragmentation, can anyone give me some pointers on how to identify the = problem correctly and a possible solution or how I might go about fixing = it? Many thanks for your time. Regards, Kevin Smith ------=_NextPart_000_0039_01C1EF5C.95F4E990 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi All,

Does anyone know about fragmented = Apache headers=20 and what "might" cause them?

I've been informed that the further the = customer is=20 away (geographically) the more fragmented the headers get to an extent = where the=20 page is not served?

I do not have any experience with = Apache headers=20 and their fragmentation, can anyone give me some pointers on how to = identify the=20 problem correctly and a possible solution or how I might go about fixing = it?

Many thanks for your time.

Regards,

Kevin = Smith

------=_NextPart_000_0039_01C1EF5C.95F4E990--