Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Date: Fri, 10 May 2002 10:14:47 -0700
From: Daniel Lopez <daniel@rawbyte.com>
To: users@httpd.apache.org
Subject: Re: Apache - Possible to Modify Header or Negate Some Apache Header
 Response?
Message-ID: <20020510171447.GA1221@rawbyte.com>
References: <008501c1f7fc$747d6a00$2101a8c0@mit001>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <008501c1f7fc$747d6a00$2101a8c0@mit001>
User-Agent: Mutt/1.3.28i


There is a space before the Content-type: text/vnd.wap.wml line
Is that intentional or just from the copy and paste?
It seems to me that that file contains the Content-type header. That is
incorrect, the server should add those headers:
http://www.webreview.com/2001/02_16/developers/index02.shtml

Otherwise the client will mistake that header as part of the page content

> I posted this under an ISAPI subject - which is not really correct - so am
> reposting under what I hope might be more pertinent to the question!
> 
> Having looked at a problem with the use of  DLL's on a WIN32 version of
> Apache, which is now solved using ISAPI, I have observed the following from
> the header (examples are Apache and IIS):
> ========================================
> APACHE
> 
> HTTP/1.1 200 OK
> Date: Thu, 09 May 2002 15:52:12 GMT
> Server: Apache/2.0.36 (Win32)
> Connection: close
> Content-Type: application/octet-stream
> 
> Content-type: text/vnd.wap.wml
> 
> <?xml version="1.0"?>
> ========================================
> 
> ========================================
> IIS
> 
> HTTP/1.0 200 OK
> Server: Microsoft-IIS/4.0
> Date: Thu, 09 May 2002 23:51:41 GMT
> Set-cookie: ASKALEXTT=1020988301;
> 
> Content-type: text/vnd.wap.wml
> 
> <?xml version="1.0"?>
> ========================================
> 
> In the IIS response, the server does not return an end of encoding content
> type, allowing us to send our own, demonstrated here by us calling for a WAP
> formatted .wml file which the .dll does, it also returns a cookie - which we
> want to retain. In this example, branding up the server allows us to return
> browser formatted data, Wap formatted data, or data for specific devices, so
> header information is critical for us.
> 
> In the Apache header, the return of the Content-Type:
> application/octet-stream actually causes a problem in that we are unable to
> modify the header from the .dll and this disrupts the intended action.
> 
> My question is thus: Is there any way that we can tell Apache not to send
> back the Content type and allow the .dll to add or modify the header before
> it is returned? Or, are we breaking some fundamental law with HTTP Servers
> by attempting this action?
> 
> Once again thanks in advance for any pointers or information.
> 
> 
> Best Regards,
> 
> Steve Leach
> Network Manager
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org