{'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

rfj1001 · Post by **rfj1001** » 27 Sep 2021 14:10

As of today I'm consistently getting the above error message when I cllick on the fmp matches in the FH focus window. MyH matches is working as normal as is the fmp website if I go straight to it.

Has anybody come across this or knows how to fix it. I know there was a large cumulative update last night of Win10.

The full url that causes the error message is https://www.findmypast.co.uk/hints-ui/# ... status=New

Thanks

YouTube · Post by **Jane** » 27 Sep 2021 14:16

Have you tried deleting all the Find My Past Cookies on your web browser?

Post by **tatewise** » 27 Sep 2021 15:23

Are you using FH v7.0.8.2 that uses the Edge browser in the Web Search Window?
Whenever I try such FMP Hints it displays a 'But first, cookies' message with options 'Edit settings' and 'That's fine'.
My URL is https://www.findmypast.co.uk/hints-ui/# ... &_k=q8gtyj similar to yours.

rfj1001 · Post by **rfj1001** » 27 Sep 2021 15:41

Thanks Jane - that sorted it. Mike, I was using chrome but thanks for the input anyway.

Kylie · Post by **Kylie** » 17 Oct 2021 06:14

Hi

I am also getting this error. I've cleared ALL cookies from Chrome browser, I've changed to Allow ALL cookies, I am still getting the bad request error message.

I am using FH v7.0.8.2 & FMP & My Heritage hints are set to open externally in Chrome.

Thanks for any other hints that can be offered.

Kylie

Post by **tatewise** » 17 Oct 2021 11:31

Do FMP and MyHeritage open in Chrome if you visit those websites directly and not via FH Hints?

Kylie · Post by **Kylie** » 18 Oct 2021 09:16

Yes they do.

Kylie · Post by **Kylie** » 19 Oct 2021 00:34

Slight update - FMP hints are now suddenly working.

Though just before I clicked a hint, I noticed small pop window from FH saying MyHeritage not working too many errors. (or similar).

Kylie · Post by **Kylie** » 27 Nov 2021 00:16

My Heritage is now working again, however FMP is once again showing Bad Request message. I've done the clearing of cookies, FH hints opens in external chrome. FMP opens if I manually type in FMP.com.au/etc into Chrome.

Thanks

Post by **pmtayifa@me.com** » 01 Jul 2022 13:13

I'm getting the same error "statusCode":400,"error":"Bad Request","message":"Invalid cookie header" when trying to access info from opening Chrome externally. I have cleared all cookies. I can access FMP hints internally and also access FMP directly via Chrome

ColinBeaver · Post by **ColinBeaver** » 15 Nov 2022 20:51

I am running V6 and having this problem i.e.

{"statusCode":400,"error":"Bad Request","message":"Invalid cookie header"}

My heritage opens OK

Cookie cleared etc

I am doing nothing differently to previous occasions went the Hints were working

Has anyone a solution

Thanks

Ossie57 · Post by **Ossie57** » 11 Dec 2022 14:03

Has anyone ever found a solution to this problem. I have exactly the same issue and have been clearing cookies, resetting and changing browers turning off and on the Internet settings in FH, all to no avail.

I have logged a ticket with FH but not sure whether it is an application issue or something that has changed in FMP?

I'm using FH version 7.0.18

Any suggestions?

Thanks.

Post by **tatewise** » 11 Dec 2022 14:23

The cause of this problem is a bit mysterious.
Please confirm you are clearing the cookies in the browser that produces the error message.
That applies to any external browser.
If using the FH internal Web Search Window that uses Microsoft Edge so its cookies need clearing.

Ossie57 · Post by **Ossie57** » 11 Dec 2022 17:02

Hi,

Thanks for your reply. I have cleared all cookies from all browsers that I use. I have changed default browsers from Firefox to Edge and back again having cleared the browser cookies numerous times. The issue seems to go away for one or two searches from within FH but then on the next (sporadically), it locks up and 'Not Responding' shows.

I'm wondering if this is an issue with FMP but not sure.

Post by **tatewise** » 11 Dec 2022 19:59

Just to be clear, if the searches are within FH in its internal Web Search Window, there is no point involving any other browser than Microsoft Edge, which is what FH uses in its internal window.

Ossie57 · Post by **Ossie57** » 12 Dec 2022 09:48

Understood, thanks. However, if I set the FH setting to open the links in the external browser, then the error still occurs with the details posted in my initial post.

Nevertheless, I normally have the setting to open within the FH internal browser but as far as I can see there is no way of clearing the cookies for that unless FH is using the Edge browser from within my PC.

This is a very annoying issue. I'm hoping there is a response from FH support today. If so I'll post their reply.

Post by **tatewise** » 12 Dec 2022 11:22

Yes, it is an annoying problem that presumably involves some interaction with FMP that goes wrong.

As I said, the FH internal Web Search Window uses the Microsoft Edge browser, so clearing its cookies should help.

Ossie57 · Post by **Ossie57** » 12 Dec 2022 16:13

As an update, FH support stated that they had not heard of this issue before...They suggested that I uninstall and re-install FH.

Having carried out further tests the issue is NOW only happening when using the internal browser. The results show when using the external browser.

I will try the uninstall later this evening.

Ossie57 · Post by **Ossie57** » 12 Dec 2022 17:37

Tried the uninstall and re-install and the problem remains!

Have reported back to FH Support to see what else they suggest.

ColinBeaver · Post by **ColinBeaver** » 15 Dec 2022 11:48

I have always clear my browser of cookie I received this error code.

ColinBeaver · Post by **ColinBeaver** » 15 Dec 2022 11:52

I have always regularly clear my browser of cookies, and I received this error code.

With no change in my routine the error code no longer occurs

Running V6

Family Historian User Group

* {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

{'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'

Re: {'statusCode':400,'error':'Bad Request','message':'Invalid cookie header'