Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 90328 invoked by uid 500); 30 Mar 2000 14:31:42 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 90305 invoked from network); 30 Mar 2000 14:31:31 -0000 Sender: mjs Message-ID: <38E3652F.970D082@iii.co.uk> Date: Thu, 30 Mar 2000 15:31:11 +0100 From: Michael Smith X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Apache Group Mailing List Subject: Wap gateways and HTTP_HOST Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Having just set up our wap service, we've discovered that a lot of "wap" requests come through with HTTP_HOST set to servername:portnumber (e.g. mobile.iii.co.uk:80). This is the first time I've seen this, and it did break our architecture for a while, before we got on top of it. It seems like this is produced by the Wap gateways (I know next to nothing about Wap, but am learning fast!). Are they breaching HTTP/1.1, and if so, any suggestions as to how to handle this? Mike