forum.e-valid.com

I am trying out the eval version for Site Analysis, but it's not producing
the results I expect.

I am scanning http://online.vodafone.co.uk, looking for pages which do NOT
contain the string "dcsCollect()". The report lists a lot of pages, but
when I click on them and view the source, I can see that in fact they DO
have the string (right near the bottom).

I've tried slight variations on this string (such as omitting the parentheses)
but it made no difference. I was using "Background (Normal)" mode; I've just
tried "Full Browser Mode" and that looked like it was OK...

Can you please advise?

Good work in driving eValid.

Yes, you have found that detailed string searches like the one you're
doing require the Full Browser Mode. That is because to identify
a page that does NOT contain "dcsCollect()" eValid has to scan the
actual delivered HTML page, and it does that using the internal
DOM to read the innerText atribute contents.

So, you've found the right mode -- Full Browser Mode -- which is the
MAIN mode of operation for site analysis...it is the strongest and
most flexible mode.

The other modes are included in case you need to run a very fast,
less detailed, scan...

__________________
The eValid Team

Thanks for running that scan. I've had a look at the results, and there
are a few erroneous URLs in the strings report. For example
http://online.vodafone.co.uk/dispatch/P ... dafone/wrp?
_nfpb=true&_pageLabel=template12&pageID=OS_0034 (near the bottom of the list).

If you open the source of this page, you will see a reference to
dcsCollect near the bottom of the page.

Obviously I'm concerned that we get 100% accuracy, so can you
investigate what's gong on?

Thanks,

Thanks for writing.

I'm glad you like the larger report...it demonstrates what the
eValid site analysis feature can do.

I'll ask some of the technical guys to look into this, but
one thing I might suggest just off the top of my head is that
the page analysis IS done dynamically, that is, from what is
actually sent over the wire.

We often see this happening, that is, slightly different results when
a site is being updated -- and this phenomena is amplified if
the web site is a "full dynamic" site.

So it could be that at the time eValid made the "can't find this string"
determination it really wasn't there, but was added later.

Do you know, in the case of online.vodafone.co.uk, if the pages
were being updated at the time scan was being done?

___________
The eValid Team