----- Original Message ----- 
From: "sebb" <[EMAIL PROTECTED]>
To: "JMeter Users List" <[email protected]>
Sent: Tuesday, March 01, 2005 7:16 PM
Subject: Re: <link> element should be ignored


> On Tue, 1 Mar 2005 14:24:10 -0500, joelsherriff
> <[EMAIL PROTECTED]> wrote:
> > In addition to <link>, <frame>s are also not processed correctly if
download
> > embedded resources is checked, or at least weren't as of 2.0.1.
> > Specifically, any src= attributes inside <frames> are ignored.
>
> OK - I'll look at that as well.
>
> > I was paid to fix a few things such as this and implement a few others
and I
> > still haven't been released to give the code away or I would have
already.
>
> If there are any other bugs you have fixed that are not documented,
> hopefully you would be allowed to report them at least, even if you
> cannot provide patches?

Let me see if I can get permission, there's not much that I haven't already
mentioned on this
list.  "They" might think I've already said too much, but the longer the
wait the further the
public code gets from my copy and the harder it'll be to re-integrate the
changes so it's in
their best interests to get as many of the changes as possible into the
public code.

> > But, I think I can describe the cache that I implemented in the hopes
that
> > someone else will do the same so that everyone can use it.  It is a very
> > small amount of code and very simple to implement.
> >
> > 99% (if not 100%) of the things that should be cached that impact a test
> > have a content-type that starts with "image/".  I can't remember the
last
> > time I saw a "text/" type that should be cached.  What I did was to copy
the
> > cookie manager code and create a cache manager.  If there is one (a
cache
> > manager), then for every response that has a content type that starts
with
> > "image/", save the last modified time and the full url (not relative
url).
> > For every request sent, see if the manager has a matching url.  If so, s
tick
> > an If-modified-since into the request headers using the last-modified
time
> > saved by the manager.  This way we get 304 Not Modified responses
instead of
> > fetching the whole thing.  There are other small details like stripping
> > other caching tags from the headers, clearing the cache after each
iteration
> > (optional so needs a checkbox on the manager dialog) and removing 304
(Not
> > Modified) from the list of REDIRECT_CODES since it really isn't a
> > redirection in the first place.
>
> Sounds good - thanks!

You're welcome, hope it helps.

> [I think I may already have fixed the 304 problem]

Excellent (as said by Mr Burns)



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to