nice!-IgorOn 1/5/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
i already have an partial implementation ready.Now there will be no difference for a WebPage when it is rendered. It will always be a WebResponse (people where complaining that sometimes it isnot a webresponse and then they also can't
i already have an partial implementation ready.Now there will be no difference for a WebPage when it is rendered. It will always be a WebResponse (people where complaining that sometimes it isnot a webresponse and then they also can't get the httpservletresponse when the need it)
i now replace it w
thats why i said maybe we should provide a datastructure just for this instead of letting the user mock response objects.something like Headers getHeaders() in the page and Headers has addHeader(..). that way we can store it with the buffered response or output it based on the render strategy
-Igor
hmm i checked this.But what is currently the preferred way to set response headers in Page.configureResponse()?check if the Response object is a WebResponse? And then call there setHeader(String,String)?Or even call
webResponse.getHttpServletResponse()and do it directly in there?Then i think in re
Hi,
maybe it would be worth thinking about also adding an abstracted way
to set the cache settings for the client for WebPages which could
default to don't cache at all... Because everytime when the browser
caches without the developer thinking about possible side effects,
something could go wrong
i will see if i can hold on to the header settings in a redirect to buffer.On 1/4/06, Igor Vaynberg <[EMAIL PROTECTED]
> wrote:maybe we need to rethink how we allow users to set headers. the redirect_to_buffer is broken because it just spits out the buffer w/out the headers that were set on the pag
maybe we need to rethink how we allow users to set headers. the redirect_to_buffer is broken because it just spits out the buffer w/out the headers that were set on the page, so it doesnt really record the entire state. it is worse because it is our default render strategy.
somehow we need to recor
Hi,
ok, I investigated this a bit further. I just saw Safari caching pages
which have urls like "http://localhost:8080/xxx_intranet/?path=16";
without taking the session into account. This was the reason for the
odd behaviour my users got sometimes (clicking on links that just were
not in the page
Hi,
what about the KDE browser Konqueror? Aren't Safari and Konqueror both
based on WebKit?
Maybe Konqueror has the same problem...
- Johannes.
Ralf Ebert wrote:
Hi,
I tried to investigate this problem a bit further after a user
complaining about a bug which seems to be related to this (I
can you tweak header cache settings somehow?configureResponse of page and then using a WebResponse object.The problem is if you use redirect_to_buffer you don't have a webresponse object when rendering i think.
So you can't really set the headers currentlyjohanOn 12/22/05, Ralf Ebert <[EMAIL PROTE
Hi,
I tried to investigate this problem a bit further after a user
complaining about a bug which seems to be related to this (I found
exceptions in the log like "No component found for 1:xxx:3:linkYyy").
This is very strange, Safari caches all pages which only have a
?path=xxx page (when going bac
11 matches
Mail list logo
