Re: [Webunitproj-users] META-Refresh support..

[Doron <dg...@sh...>]

Hi,

	You need to flush the page cache. (there is a method for that
somewhere). Essentially the first page you get is cached by webunit in
order to give you fast responses. A method is provided to flush this (as
I recall). Its been a while since I played with it. If this is not it
let me know.


				-Doron


On Thu, 2003-04-24 at 17:53, Nic Pottier wrote:
> Howdy.
> 
> I've had great luck using the enterprise webunit package to test a project I'm working on.  The interface is simple and clean, and we're able to test our product despite it's heavy use of javascript which did not work without testers.  So in short, kudos!
> 
> Now of course, with any kudos there is the obligatory caveat.  One problem we have is that we use meta-refresh'es in order to poll for time consuming operations.  IE, the user takes an action which might take 20 seconds or so, and they are taken to a 'processing' page or the like, which polls by reposting to itself every 2 seconds until the process is complete, at which time it again uses a meta refresh tag to push itself to the final destination page.
> 
> Although IE correctly deals with this while running in the webunit context, I am unable to get the 'refreshed' page from webunit.  The WebResponse I get is always the original page.  I've poked around in the API and haven't seen any obvious way to work around this.   Am I missing something here, or is this just an 'undocumented feature'. ;)
> 
> Thanks again for such a great tool,
> 
> -Nic
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Webunitproj-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webunitproj-users