I keep getting the following message on the NRE website:

Bad Request
Your browser sent a request that this server could not understand.
Size of a request header field exceeds server limit.

Is there a problem at the moment?

In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:

>I keep getting the following message on the NRE website:
>
>Bad Request
>Your browser sent a request that this server could not understand.
>Size of a request header field exceeds server limit.
>
>Is there a problem at the moment?

It's a site where I get more than the usual number of technical
glitches. Normally they seem to be it wrestling unsuccessfully
with too many cookies. I think they got the apprentices in as
webmasters.

[Working as fine as it ever does, from here right now]
--
Roland Perry

On Mon, 24 Apr 2023 07:06:11 +0100, Roland Perry <roland@perry.uk>
wrote:

>In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
>Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:
>
>>I keep getting the following message on the NRE website:
>>
>>Bad Request
>>Your browser sent a request that this server could not understand.
>>Size of a request header field exceeds server limit.
>>
>>Is there a problem at the moment?
>
>It's a site where I get more than the usual number of technical
>glitches. Normally they seem to be it wrestling unsuccessfully
>with too many cookies. I think they got the apprentices in as
>webmasters.
>
>[Working as fine as it ever does, from here right now]

Thanks. Still not working for me. It gets stuck at 'Loading
stations' (Chrome).

I may have an arcane ticketing question for you later !!!

On 24/04/2023 09:24, Scott wrote:
> On Mon, 24 Apr 2023 07:06:11 +0100, Roland Perry <roland@perry.uk>
> wrote:
>
>> In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
>> Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:
>>
>>> I keep getting the following message on the NRE website:
>>>
>>> Bad Request
>>> Your browser sent a request that this server could not understand.
>>> Size of a request header field exceeds server limit.
>>>
>>> Is there a problem at the moment?
>>
>> It's a site where I get more than the usual number of technical
>> glitches. Normally they seem to be it wrestling unsuccessfully
>> with too many cookies. I think they got the apprentices in as
>> webmasters.
>>
>> [Working as fine as it ever does, from here right now]
>
> Thanks. Still not working for me. It gets stuck at 'Loading
> stations' (Chrome).
>
> I may have an arcane ticketing question for you later !!!

It works fine for me on Chromium (Linux) for me this morning.

On 24/04/2023 09:24, Scott wrote:
> On Mon, 24 Apr 2023 07:06:11 +0100, Roland Perry <roland@perry.uk>
> wrote:
>
>> In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
>> Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:
>>
>>> I keep getting the following message on the NRE website:
>>>
>>> Bad Request
>>> Your browser sent a request that this server could not understand.
>>> Size of a request header field exceeds server limit.
>>>
>>> Is there a problem at the moment?
>>
>> It's a site where I get more than the usual number of technical
>> glitches. Normally they seem to be it wrestling unsuccessfully
>> with too many cookies. I think they got the apprentices in as
>> webmasters.
>>
>> [Working as fine as it ever does, from here right now]
>
> Thanks. Still not working for me. It gets stuck at 'Loading
> stations' (Chrome).
>
> I may have an arcane ticketing question for you later !!!

Sorry, all trains to Arcane are cancelled till further notice.

--
Graeme Wall
This account not read.

On 24 Apr 2023 at 08:06:11 CEST, "Roland Perry" <roland@perry.uk> wrote:

> In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
> Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:
>
>> I keep getting the following message on the NRE website:
>>
>> Bad Request
>> Your browser sent a request that this server could not understand.
>> Size of a request header field exceeds server limit.
>>
>> Is there a problem at the moment?
>
> It's a site where I get more than the usual number of technical
> glitches. Normally they seem to be it wrestling unsuccessfully
> with too many cookies. I think they got the apprentices in as
> webmasters.
>
> [Working as fine as it ever does, from here right now]

I've been giving NRE some hammering in the last 48 hours planning our trip
back from Portsmouth to Liverpool in mid-May.

Without the Nuneham viaduct route it looks as though the only realistic option
is via London, which I originally hoped to avoid, since we will have lots of
luggage.

But I've been feeding it all kinds of options, editing journeys, routes and
times, and I have to say it has been entirely reliable.

In message <Bsw1M.3091681$%ng4.1173711@fx09.ams1>, at 14:35:13 on Mon,
24 Apr 2023, Ken in Caen <kwelsby@gmail.com> remarked:
>On 24 Apr 2023 at 08:06:11 CEST, "Roland Perry" <roland@perry.uk> wrote:
>
>> In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
>> Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:
>>
>>> I keep getting the following message on the NRE website:
>>>
>>> Bad Request
>>> Your browser sent a request that this server could not understand.
>>> Size of a request header field exceeds server limit.
>>>
>>> Is there a problem at the moment?
>>
>> It's a site where I get more than the usual number of technical
>> glitches. Normally they seem to be it wrestling unsuccessfully
>> with too many cookies. I think they got the apprentices in as
>> webmasters.
>>
>> [Working as fine as it ever does, from here right now]
>
>I've been giving NRE some hammering in the last 48 hours planning our trip
>back from Portsmouth to Liverpool in mid-May.
>
>Without the Nuneham viaduct route it looks as though the only realistic option
>is via London, which I originally hoped to avoid, since we will have lots of
>luggage.
>
>But I've been feeding it all kinds of options, editing journeys, routes and
>times, and I have to say it has been entirely reliable.

A better planning site (more options):

https://trainscanbecheaper.info/default.aspx
--
Roland Perry

Ken in Caen <kwelsby@gmail.com> wrote:
> On 24 Apr 2023 at 08:06:11 CEST, "Roland Perry" <roland@perry.uk> wrote:
>
>> In message <ps3b4i165dasptnanb3qoikmi3bstmsoa6@4ax.com>, at 21:07:21 on
>> Sun, 23 Apr 2023, Scott <newsgroups@gefion.myzen.co.uk> remarked:
>>
>>> I keep getting the following message on the NRE website:
>>>
>>> Bad Request
>>> Your browser sent a request that this server could not understand.
>>> Size of a request header field exceeds server limit.
>>>
>>> Is there a problem at the moment?
>>
>> It's a site where I get more than the usual number of technical
>> glitches. Normally they seem to be it wrestling unsuccessfully
>> with too many cookies. I think they got the apprentices in as
>> webmasters.
>>
>> [Working as fine as it ever does, from here right now]
>
> I've been giving NRE some hammering in the last 48 hours planning our trip
> back from Portsmouth to Liverpool in mid-May.
>
> Without the Nuneham viaduct route it looks as though the only realistic option
> is via London, which I originally hoped to avoid, since we will have lots of
> luggage.
>
> But I've been feeding it all kinds of options, editing journeys, routes and
> times, and I have to say it has been entirely reliable.
>

Depends if you are prepared to trade ~40 mins longer journey time via
Bristol (plus an additional change at Birmingham) for avoiding crossing
London.

Anna Noyd-Dryver

On 23/04/2023 21:07, Scott wrote:
> I keep getting the following message on the NRE website:
>
> Bad Request
> Your browser sent a request that this server could not understand.
> Size of a request header field exceeds server limit.
>
> Is there a problem at the moment?

I get that all the time. Along with randomly switching to a Sunday, and
deciding "now" is in the past.
--
Arthur Figgis

On 23/04/2023 21:07, Scott wrote:
> I keep getting the following message on the NRE website:
>
> Bad Request
> Your browser sent a request that this server could not understand.
> Size of a request header field exceeds server limit.
>
> Is there a problem at the moment?

I've had this occasionally, but it then goes away the next day. I *think* it's some incompatibility between the rather demanding server they use and Firefox, which is the browser I tend to use most often. I complained to the NR website help service who in the past have been helpful but got nowhere. It would be nice to know what's causing it, and the cure.

--
Clive Page

On 25 Apr 2023 at 11:18:24 PM EEST, "Clive Page" <usenet@page2.eu> wrote:

> On 23/04/2023 21:07, Scott wrote:
>> I keep getting the following message on the NRE website:
>>
>> Bad Request
>> Your browser sent a request that this server could not understand.
>> Size of a request header field exceeds server limit.
>>
>> Is there a problem at the moment?
>
> I've had this occasionally, but it then goes away the next day. I *think*
> it's some incompatibility between the rather demanding server they use and
> Firefox, which is the browser I tend to use most often. I complained to the NR
> website help service who in the past have been helpful but got nowhere. It
> would be nice to know what's causing it, and the cure.

It's usually one of the Cookie headers that ends up too long, often because of
a coding bug in the site; accidentally (or intentionally without thinking
about it...) appending something to a cookie on every request instead of
overwriting it, and then eventually the cookie gets to be more than whatever
the server's limit is (usually in the order of 4K or 8K.)

TL;DR: Try clearing cookies.

On Tue, 25 Apr 2023 21:36:41 -0000 (UTC), Clank
<clank75@googlemail.com> wrote:

>On 25 Apr 2023 at 11:18:24 PM EEST, "Clive Page" <usenet@page2.eu> wrote:
>
>> On 23/04/2023 21:07, Scott wrote:
>>> I keep getting the following message on the NRE website:
>>>
>>> Bad Request
>>> Your browser sent a request that this server could not understand.
>>> Size of a request header field exceeds server limit.
>>>
>>> Is there a problem at the moment?
>>
>> I've had this occasionally, but it then goes away the next day. I *think*
>> it's some incompatibility between the rather demanding server they use and
>> Firefox, which is the browser I tend to use most often. I complained to the NR
>> website help service who in the past have been helpful but got nowhere. It
>> would be nice to know what's causing it, and the cure.
>
>It's usually one of the Cookie headers that ends up too long, often because of
>a coding bug in the site; accidentally (or intentionally without thinking
>about it...) appending something to a cookie on every request instead of
>overwriting it, and then eventually the cookie gets to be more than whatever
>the server's limit is (usually in the order of 4K or 8K.)
>
>TL;DR: Try clearing cookies.

And with Ffox, one is able to kill cookies routinely on closing... and
IMO should.

On 25 Apr 2023 17:40:33 -0700 Nobody wrote:
>On Tue, 25 Apr 2023 21:36:41 -0000 (UTC), Clank
><clank75@googlemail.com> wrote:
>
>>TL;DR: Try clearing cookies.

Which in Firefox can be done - just for that site - by clicking or tapping
on the padlock to the left of the URL bar.

This 20 year old bookmarklet will display the site's cookies:
https://www.squarefree.com/bookmarklets/misc.html#view_cookies
(Not on mobile, though.)

>
>And with Ffox, one is able to kill cookies routinely on closing... and
>IMO should.

If you don't mind being logged out of many sites.

--
(Remove numerics from email address)

On Sun, 23 Apr 2023 21:07:21 +0100, Scott
<newsgroups@gefion.myzen.co.uk> wrote:

>I keep getting the following message on the NRE website:
>
>Bad Request
>Your browser sent a request that this server could not understand.
>Size of a request header field exceeds server limit.
>
>Is there a problem at the moment?
>
Not just at the moment. The NR site manages to choke browsers with its
cookies and you have to purge them just for that site. It also fights
with Firefox so you can get more success using a different browser.