Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Errors-To: <simon@zapnetworks.com>
Reply-To: <simon@zapnetworks.com>
From: "Simon Waddington" <simon@zapnetworks.com>
To: <cocoon-dev@xml.apache.org>
Subject: RE: WAP and how to set the content-location...
Date: Wed, 16 Feb 2000 13:12:51 -0800
Message-ID: <91E0EC9A2996D311A59C0050DA2E0A1C03CFA8@BARILOCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <91E0EC9A2996D311A59C0050DA2E0A1C03F417@BARILOCHE>
Importance: Normal

Ted, you're right!  I've been using the 4.0-beta simulator that only works
in direct mode (which is actually more useful for debugging since I can dump
the source).  Now I've switched to the older 3.2 simulator in provisioned
mode via UPs servers and the caching seems to be behaving properly.

Thanks for pointing this out.

Simon.


-----Original Message-----
From: Ted [mailto:ted@gs2admin1.e-meet.com]
Sent: Wednesday, February 16, 2000 12:13 PM
To: cocoon-dev@xml.apache.org
Subject: Re: WAP and how to set the content-location...


When you test this, I presume that you provision yourself to pass
through the gateway when you are using the simulator? I am not seeing
this behavior in our implementation. It does cache, though, when I try
to access the server directly, not passing through dev2.phone.com
gateway.

Dr. Teddy Achacoso
GroupServe, Inc.

Simon Waddington wrote:
>
> Hi folks,
>
> I'm trying to figure out how to set the response content-location header.
> I've tried the obvious of putting:
>
> <xsp:logic>
>  response.setHeader ("Cache-Control", "max-age=0");
>  response.setHeader ("Content-Location", String.valueOf
> (System.currentTimeMillis()));
>  Date now = new Date ();
>  long nowTime = now.getTime();
>  response.setDateHeader("Date", nowTime);
> </xsp:logic>
>
> in my .xml file that is getting served up. This should give every response
a
> unique content location which is sadly the only way to convince Unwired
> Planet (Phone.com) powered WAP devices to not cache server responses.
> However this seems to have no effect as after returning the result the
> browser keeps hitting the cache and not my server.
>
> I'm using the Tomcat 3.1 server and Cocoon 1.6.1.  Has anyone else managed
> to do this sucessfully?
>
> Simon