Re: URL lengths

On 30 Nov, Tim Hill wrote in message <56a3223323...@timil.com>: > I just can't believe that a URL can contain 33% more letters than the King > James Bible's 3,116,480. > > "four gigabytes per URL" > > LOL In RISC OS terms, it's another way of saying "limited by available memory"... --

Re: URL lengths

On 30 Nov, Harriet Bazley wrote in message : > On 28 Nov 2017 as I do recall, > Daniel Silverstone wrote: > > > I don't believe we limit URL length per-se, though they get interned and > > as such four gigabytes per URL is probably the absolute

Re: URL lengths

In article <56a1aa7e00joh...@ukgateway.net>, John Williams wrote: > What is the maximum URL length (including POST data) that NetSurf can > handle? What may be relevant is the following entry from my web server error logs: 2017-10-02 02:57:45: (response.c.553) file not

Re: URL lengths

On Thu, Nov 30, 2017 at 02:32:29PM +, Tim Hill wrote: > > I just can't believe that a URL can contain 33% more letters than the > King James Bible's 3,116,480. > > "four gigabytes per URL" It's probably much greater than that on modern systems, too! B.

Re: URL lengths

In article , Harriet Bazley wrote: > On 28 Nov 2017 as I do recall, Daniel Silverstone wrote: > > On Mon, Nov 27, 2017 at 18:08:46 +, John Williams wrote: > > > What is the maximum URL length (including POST data) that NetSurf >

Re: URL lengths

On 28 Nov 2017 as I do recall, Daniel Silverstone wrote: > On Mon, Nov 27, 2017 at 18:08:46 +, John Williams wrote: > > What is the maximum URL length (including POST data) that NetSurf can > > handle? > > I don't believe we limit URL length per-se, though they get interned and as

Re: URL lengths

In article <20171128115425.22cudniq3zrfba3l@somnambulist.local>, Daniel Silverstone wrote: > I don't believe we limit URL length per-se, though they get interned and > as such four gigabytes per URL is probably the absolute limit. In > addition, POST data is

Re: URL lengths

On Mon, Nov 27, 2017 at 18:08:46 +, John Williams wrote: > What is the maximum URL length (including POST data) that NetSurf can > handle? I don't believe we limit URL length per-se, though they get interned and as such four gigabytes per URL is probably the absolute limit. In addition, POST

Re: URL lengths

On Mon, Nov 27, 2017 at 06:08:46PM +, John Williams wrote: > An genuine real-life number would be better! >From memory, they are dynamically allocated as needed and can be of arbitrary length. This is a lot more efficient than using statically-sized buffers for the worst common case,

Re: URL lengths

In message <56a1b699dcjoh...@ukgateway.net> John Williams wrote: > In article <0612b1a156.ga...@wra1th.plus.com>, > Gavin Wraith wrote: > So you're suggesting that I measure each URL length first, perhaps BGETting > it until I encounter

Re: URL lengths

On 27 Nov, John Williams wrote in message <56a1b699dcjoh...@ukgateway.net>: > In article <0612b1a156.ga...@wra1th.plus.com>, >Gavin Wraith wrote: > > > I would DIM buffers for URLs from the heap as you need them. > > So you're suggesting that I measure each URL

Re: URL lengths

In article <0612b1a156.ga...@wra1th.plus.com>, Gavin Wraith wrote: > From a quick glance at the NetSurf 3.7 sources I would guess that the > answer rather depends on which platform, and then on the particular > machine NetSurf is running on. I am, of course, running

Re: URL lengths

In message <56a1aa7e00joh...@ukgateway.net> John Williams wrote: > What is the maximum URL length (including POST data) that NetSurf can > handle? >From a quick glance at the NetSurf 3.7 sources I would guess that the answer rather depends on which platform, and

URL lengths

I'm writing a little menu program to generate URL index pages. It's to make URLs easily available to my Linux machine if there are any problems with a page/site under NetSurf. What is the maximum URL length (including POST data) that NetSurf can handle? My program is taking text URLs, Ant URL