Re: Form submission timeouts
On 15 Aug 2017 as I do recall, Harriet Bazley wrote: > On 11 Aug 2017 as I do recall, > Dave Higton wrote: > > > The numbers and the symptoms fit with it being an MTU problem. I > > had something like it a few years ago - unfortunately too long ago > > for me to remember much about it or its solution. [snip] > It doesn't (mercifully) seem to affect Netsurf's form submission on any > other sites (e.g. I can still post blog entries). Just pages on that one > server/set of servers. > In fact, I'm still able to upload data of any length onto this same site using the 'Drop file here' box (input type="file") - it's very specifically the submission of form data via a multi-line text area in Netsurf that is timing out. -- Harriet Bazley == Loyaulte me lie == My opinions may have changed, but not the fact that I am right.
Re: Form submission timeouts
On 11 Aug 2017 as I do recall, Rob Kendrick wrote: [snip] > Something that has bitten be before is where automatic path MTU > discovery does not work (and I suspect it doesn't on RISC OS), and your > ISP does not support end-to-end 1500 byte MTUs (many do not). > > The solution is to set your whole LAN's MTU to 1400 or similar, although > setting it only on the RISC OS machines may be sufficient (and not > needed on VirtualAcorn because that proxies Windows's IP stack which is > full-featured and conforming) assuming the problem is only sending large > packets, not receiving them. > I wouldn't know where to configure that, I'm afraid; the network consists of Ethernet cables emerging from our Virgin Hub and plugging into the RISC OS computers and the printer. -- Harriet Bazley == Loyaulte me lie == I like work; it fascinates me; I can sit and look at it for hours.
Re: Form submission timeouts
On 11 Aug 2017 as I do recall, Dave Higton wrote: [snip] > I apologies that my response here won't be as useful as I want it to > be. > > The numbers and the symptoms fit with it being an MTU problem. I > had something like it a few years ago - unfortunately too long ago > for me to remember much about it or its solution. > > Has anything changed recently about your internet provision (e.g. a > new router, or service from a new provider), or something about the > platform from which you're sending? Nothing whatsoever has changed at this end. And that one specific site just stopped working overnight, with no announcement of any changes and no new features appearing. It doesn't (mercifully) seem to affect Netsurf's form submission on any other sites (e.g. I can still post blog entries). Just pages on that one server/set of servers. -- Harriet Bazley == Loyaulte me lie == Cole's Law: Thinly sliced cabbage.
Re: Form submission timeouts
In article <20170811163021.gk7...@platypus.pepperfish.net>, Rob Kendrick wrote: > On Fri, Aug 11, 2017 at 05:16:09PM +0100, Dave Higton wrote: > > > > If anyone reading this thread can shed any light on MTU issues, how > > to diagnose them and how to fix them, it would be very helpful. > Something that has bitten be before is where automatic path MTU > discovery does not work (and I suspect it doesn't on RISC OS), and your > ISP does not support end-to-end 1500 byte MTUs (many do not). > The solution is to set your whole LAN's MTU to 1400 or similar, > although setting it only on the RISC OS machines may be sufficient (and > not needed on VirtualAcorn because that proxies Windows's IP stack > which is full-featured and conforming) assuming the problem is only > sending large packets, not receiving them. I find it fascinating that my ISP's web support MTU is variously 1454, 1458, 1492 and 1500. This is dependent on hardware - the last one being a generic setting for 'none of the above routers'. Funny how the original 'net developers opted for and MTU of around 1500. Anyone who's had a computer for more than a few weeks ought to wonder why it's not 1024. -- Tim Hill timil.com : tjrh.eu : butterwick.eu : blue-bike.uk : youngtheatre.co.uk
Re: Form submission timeouts
On Fri, Aug 11, 2017 at 05:16:09PM +0100, Dave Higton wrote: > > If anyone reading this thread can shed any light on MTU issues, > how to diagnose them and how to fix them, it would be very > helpful. Something that has bitten be before is where automatic path MTU discovery does not work (and I suspect it doesn't on RISC OS), and your ISP does not support end-to-end 1500 byte MTUs (many do not). The solution is to set your whole LAN's MTU to 1400 or similar, although setting it only on the RISC OS machines may be sufficient (and not needed on VirtualAcorn because that proxies Windows's IP stack which is full-featured and conforming) assuming the problem is only sending large packets, not receiving them. B.
Re: Form submission timeouts
In message <9ceaa96956.harr...@blueyonder.co.uk> Harriet Bazley wrote: >On 9 Aug 2017 as I do recall, > Harriet Bazley wrote: > >> Currently I just get a time-out error after about twenty seconds if I >> attempt to send messages of over 1,485 characters via a PM or a post of >> more than 1,343 characters to a forum. > >I've since discovered that the site's document-editing feature is timing out >as well. Previously it was possible to do basic editing on the raw HTML of >a previously submitted document via Netsurf - now you can edit but can't >save the result. I haven't bothered testing to see what the triggering >length on this feature is since an HTML page of under 1K in total length is >never going to be of much use in practice... > >So it looks as if all multi-line text icons are being affected. I apologies that my response here won't be as useful as I want it to be. The numbers and the symptoms fit with it being an MTU problem. I had something like it a few years ago - unfortunately too long ago for me to remember much about it or its solution. Has anything changed recently about your internet provision (e.g. a new router, or service from a new provider), or something about the platform from which you're sending? I used to think that the MTU had no practical effect - above this value, packets would be automatically fragmented and equally automatically re-assembled. But my lesson was that it doesn't work like I thought. You might try looking at the various interfaces along the network to see if the MTU of any of them can be altered. If anyone reading this thread can shed any light on MTU issues, how to diagnose them and how to fix them, it would be very helpful. Dave
Re: Form submission timeouts
On 9 Aug 2017 as I do recall, Harriet Bazley wrote: > Currently I just get a time-out error after about twenty seconds if I > attempt to send messages of over 1,485 characters via a PM or a post of > more than 1,343 characters to a forum. I've since discovered that the site's document-editing feature is timing out as well. Previously it was possible to do basic editing on the raw HTML of a previously submitted document via Netsurf - now you can edit but can't save the result. I haven't bothered testing to see what the triggering length on this feature is since an HTML page of under 1K in total length is never going to be of much use in practice... So it looks as if all multi-line text icons are being affected. -- Harriet Bazley == Loyaulte me lie == "An American is a man with two arms and four wheels".
Re: Form submission timeouts
On 10 Aug 2017 as I do recall, Harriet Bazley wrote: [snip] > (12.43) desktop/browser.c:2105 browser_window_navigate: Loading > 'https://www.fanfiction.net/pm2/post.php?rid=218867318' > (12.43) content/fetchers/curl.c:324 fetch_curl_setup: fetch 0x749465b0, > url 'https://www.fanfiction.net/pm2/post.php?rid=218867318' > (20.06) content/content.c:382 content_destroy: content 0x748be850 > https://www.fanfiction.net/static/images/favicon_2010_site.ico > (44.20) content/fetchers/curl.c:867 fetch_curl_process_headers: HTTP > status code 200 > (44.22) content/fetchers/curl.c:1040 fetch_curl_done: done > https://www.fanfiction.net/pm2/post.php?rid=218867318 > (44.22) content/fetchers/curl.c:799 fetch_curl_stop: fetch 0x749465b0, > url 'https://www.fanfiction.net/pm2/post.php?rid=218867318' > (44.23) content/content.c:76 content__init: url > https://www.fanfiction.net/pm2/post.php?rid=218867318 -> 0x747c9b40 > > The first 8 seconds are me dropping my pre-prepared message into the reply > form; the next 24 seconds are the browser waiting for curl to fetch; after > that, it's busy rendering the error page. :-( > Here's the equivalent section of log after truncating the message and posting it successfully: (16.66) desktop/browser.c:2006 browser_window_navigate: bw 0x7473dc80, url https://www.fanfiction.net/pm2/post.php?rid=218867318 (16.67) desktop/browser.c:2105 browser_window_navigate: Loading 'https://www.fanfiction.net/pm2/post.php?rid=218867318' (16.67) content/fetchers/curl.c:324 fetch_curl_setup: fetch 0x74cc62d8, url 'https://www.fanfiction.net/pm2/post.php?rid=218867318' (17.14) content/fetchers/curl.c:867 fetch_curl_process_headers: HTTP status code 200 (17.14) content/content.c:76 content__init: url https://www.fanfiction.net/pm2/post.php?rid=218867318 -> 0x748bc830 -- Harriet Bazley == Loyaulte me lie == Questions are a burden to others, but answers are a prison for oneself.
Re: Form submission timeouts
On 9 Aug 2017 as I do recall, Chris Young wrote: > On 09/08/2017 17:21, Harriet Bazley wrote: > > Over the last couple of days, Netsurf has unexpectedly started timing-out > > when you attempt to send messages of more than a certain length via the > > www.fanfiction.net website, either via the user forums or the PM system. [snip] > > I've looked at Netsurf's logs, but the failed attempts aren't showing any > > error messages other than a 20-second gap. There were site-wide problems > > with the forums recently, but this particular issue doesn't seem to be > > affecting anybody else. > > > > Do these specific byte lengths suggest anything to anyone? > > > > > Maybe similar to http://bugs.netsurf-browser.org/mantis/view.php?id=2252 ? > Set suppress_curl_debug:0 in Choices and have another look at the log file. > It does sound a bit similar, but the only effect of setting suppress_curl_debug:0 appears to have been to lengthen the timeout period: (12.43) desktop/browser.c:2105 browser_window_navigate: Loading 'https://www.fanfiction.net/pm2/post.php?rid=218867318' (12.43) content/fetchers/curl.c:324 fetch_curl_setup: fetch 0x749465b0, url 'https://www.fanfiction.net/pm2/post.php?rid=218867318' (20.06) content/content.c:382 content_destroy: content 0x748be850 https://www.fanfiction.net/static/images/favicon_2010_site.ico (44.20) content/fetchers/curl.c:867 fetch_curl_process_headers: HTTP status code 200 (44.22) content/fetchers/curl.c:1040 fetch_curl_done: done https://www.fanfiction.net/pm2/post.php?rid=218867318 (44.22) content/fetchers/curl.c:799 fetch_curl_stop: fetch 0x749465b0, url 'https://www.fanfiction.net/pm2/post.php?rid=218867318' (44.23) content/content.c:76 content__init: url https://www.fanfiction.net/pm2/post.php?rid=218867318 -> 0x747c9b40 The first 8 seconds are me dropping my pre-prepared message into the reply form; the next 24 seconds are the browser waiting for curl to fetch; after that, it's busy rendering the error page. :-( -- Harriet Bazley == Loyaulte me lie == Radioactive cats have 18 half-lives.
Re: Form submission timeouts
In article <99b0fa6856.harr...@blueyonder.co.uk>, Harriet Bazley wrote: > Do these specific byte lengths suggest anything to anyone? MTU. Though how can that...? -- Tim Hill timil.com : tjrh.eu : butterwick.eu : blue-bike.uk : youngtheatre.co.uk
Re: Form submission timeouts
On 09/08/2017 17:21, Harriet Bazley wrote: Over the last couple of days, Netsurf has unexpectedly started timing-out when you attempt to send messages of more than a certain length via the www.fanfiction.net website, either via the user forums or the PM system. PMs have an official site limit of 8000 characters (and I've successfully sent messages of up to this length before) and so far as I recall the forum post size limit is 9,999 characters. Currently I just get a time-out error after about twenty seconds if I attempt to send messages of over 1,485 characters via a PM or a post of more than 1,343 characters to a forum. This is quite limiting when attempting to reply to other users -- especially as the site rules prohibit sending more than one post in succession! Request Timeout This request took too long to process, it has been timed out by the server. If it should not be timed out, please contact the administrator of the website to increase the 'Connection Timeout' time allotted. I've looked at Netsurf's logs, but the failed attempts aren't showing any error messages other than a 20-second gap. There were site-wide problems with the forums recently, but this particular issue doesn't seem to be affecting anybody else. Do these specific byte lengths suggest anything to anyone? Maybe similar to http://bugs.netsurf-browser.org/mantis/view.php?id=2252 ? Set suppress_curl_debug:0 in Choices and have another look at the log file. Chris
Form submission timeouts
Over the last couple of days, Netsurf has unexpectedly started timing-out when you attempt to send messages of more than a certain length via the www.fanfiction.net website, either via the user forums or the PM system. PMs have an official site limit of 8000 characters (and I've successfully sent messages of up to this length before) and so far as I recall the forum post size limit is 9,999 characters. Currently I just get a time-out error after about twenty seconds if I attempt to send messages of over 1,485 characters via a PM or a post of more than 1,343 characters to a forum. This is quite limiting when attempting to reply to other users -- especially as the site rules prohibit sending more than one post in succession! Request Timeout This request took too long to process, it has been timed out by the server. If it should not be timed out, please contact the administrator of the website to increase the 'Connection Timeout' time allotted. I've looked at Netsurf's logs, but the failed attempts aren't showing any error messages other than a 20-second gap. There were site-wide problems with the forums recently, but this particular issue doesn't seem to be affecting anybody else. Do these specific byte lengths suggest anything to anyone? -- Harriet Bazley == Loyaulte me lie == "An American is a man with two arms and four wheels".
