On 22 Mar 2011  Keith & Elizabeth Hopper <[email protected]> wrote:

> On 22/03/11 23:00, Dr Peter Young wrote:
>> On 22 Mar 2011  Daniel Silverstone <[email protected]>
>> wrote:
>> 
>>> On Mon, Mar 21, 2011 at 04:44:09PM +0000, Dr Peter Young wrote:
>>>> Internal Server Error
>> 
>>> Could you please let us know which URL is causing this error, and
>>> whether or
>>> not it still does?
>> 
>> Yes, it still does. One example is
>> http://source.netsurf-browser.org/?rev=12120&view=rev
>> but any of the similar links from the test-builds page does the same.
>> This is with RISC OS NetSurf r12104. I haven't tried with Windows
>> Firefox, but am just going out for the rest of the day; I'll try
>> Windows in the evening.

>      I've just checked with Firefox 4 and it works - BUT!!!!
> After the preliminary interaction with the server, the message
> "transferring data from [netsurf server]" appeared for about five
> seconds with a blank screen. Eventually the desired page appeared.

After a long and disorganised day (I forgot to send my previous post 
before going away for the day, and haven't had time to check with 
Windows; thanks, Keith), it gets odder. I downloaded r12124 (RISC OS 
5.16) independently of the test-builds page, and find this:

I look at the download page; at the top of this I click on
http://source.netsurf-browser.org/?view=revision&revision=12124

This takes 16.2 seconds to produce anything, much longer than usual, 
and looks different from what I am used to seeing. Then click on 
"modified", and I get throbber action, but no new page, at least 
within the limits of my patience.

Something seems to be going wrong here. I know I'm ignorant about 
these things, but it's definitely not right. Expert opinion, please!

With best wishes,

Peter.

-- 
Peter   \  /      zfc Lu     \     Prestbury, Cheltenham,  Glos. GL52
and      \/ __            __  \                              England.
family   / /  \ | | |\ | /  _  \      http://pnyoung.orpheusweb.co.uk
        /  \__/ \_/ | \| \__/   \______________ [email protected]

Reply via email to