First test of 9.02 Beta 2A

[Albert Wiersch]

2) I got, as expected, a bunch of errors for the js files in the batch report. Unfortunately most content of the individual report pages was a copy of the first erroring page (a php page on a remote server reached by a redirect). The custom content was page name and time taken to analyse, i.e. nothing substantial. In other words I can't see the things that javascript lint picked up on any of those pages. On recheck I found that the add a UrL link dialog had inserted a different base address (site) to the one I was working with, so I imagine that what happened here was that when the lint found no file to analyse I got that incorrect error report.

Hi Mike,

I think all the other issues have been addressed but I am not sure about the above. Is there still an issue with the latest editor EXE and DLL I've sent you? If so, can you give me more details on how to reproduce it?

[MikeGale]

Hi,

I had destroyed the test that gave this.

I recreated it and it's still there.

I changed the description of this in a later post in the thread. See that for more details.

My new test was:

3 URL based targets.

First was an HTML page with errors.

Remaining two were non-existent *.js files.

The js files are listed with errors. Those errors are a copy of the HTML page errors.

[Albert Wiersch]

Hi Mike,

I'm having trouble reproducing this.

I created a target list with an HTML URL and a JS url and got this message in the progress window:
An error occurred for the request "http://www.htmlvalidator.com/about.js". Error: 0, Status: 404, Reason: Not Found. This target will not be processed.

I think added a link to a non-existent js file in the HTML file and just got a bad link report.

I could not find any problems.

Would it be possible for you to send more details, including your target list and the generated report files that show the problem? Thank you.

[MikeGale]

Hi Albert,

I generated the reports zipped them up with the *.lst file and checked the server using ftp. (I have access to the site I was testing.)

I then ran another test I called up the non existent js in the CSE editor.

Surprisingly I got the default page.

So it's not a CSE issue. Sorry to take your time on this.

The server (which I don't administer or set up) serves up the default page when it has some (maybe all) unknown URLs. (I was not previously aware of that approach, I though a 404 was normal!)

[Albert Wiersch]

So it's not a CSE issue. Sorry to take your time on this.

No problem! Your reports have been very helpful.

I'll consider this one closed!