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"...
--
Ste
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 limit. In
> > addition, POST data is
On 2017-11-30 14:32, 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.
Hmm; 33% more than 3,116,480 is roughly 4 MB, not GB.
--
Jeremy Nicoll - my opinions are my own
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 found ... or so: File
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.
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
> > > can handle?
> >
> > I don't believe we limit URL length per
