Your client has issued a malformed or illegal request that s all we know

Fix: YouTube Error 400 “client has issued a malformed or illegal request”

Some users have been encountering the Youtube Error 400 when visiting some or any Youtube page from a Windows PC. The error message is rather ambiguous and reads “Your client has issued a malformed or illegal request. That’s all we know”.

Looking at the status code, the error seems to indicate that Youtube serves is incapable of processing your request due to a client error. The reasons why this is commonly happening is an invalid request message, framing or a deceptive request routing.

After investigating the issue, it seems like the Youtube Error 400 is sometimes caused by a selection of cookies that are being misused. However, most of the time, the issue occurs on Chrome versions that are actively using the Great Suspender extension. As it turns out, the problem is caused by the matter in which the scroll position is recorded in the cookies. After a while, the size of the cookie will surpass the limit and the affected user will start seeing the Youtube Error 400 message.

How to fix the Youtube Error 400

As of know, there is no other way of resolving the issue than deleting the cookies responsible for the apparition of this issue. But keep in mind that unless you used some kind of Chrome extension capable of blocking the gsScrollPos cookie from exceeding the size, you’ll likely end up getting the Youtube Error 400 message again after some time.

If you’re struggling with the Youtube 400 error, the methods below will help you overcome the issue. Please follow the potential fixes below in order until you encounter a fix that manages to re-grant you the normal functionality of YouTube.

If you’re looking for a quick and easy fix, follow Method 1. If you want to specifically delete the cookies that are causing the issue without removing the rest of Youtube’s related cookies, follow Method 2.

Method 1: Deleting the gsScrollPos cookie via siteData

This first method involves launching Chrome’s SiteData page and deleting the cookie responsible for the apparition of the Youtube Error 400 manually. But keep in mind that following the steps below will delete all related Youtube cookies, not just the gsScrollPos cookie (which is responsible for this issue).

Here’s a quick guide on to do this:

Method 2: Removing the gsScrollPos cookie via Developer Tools

A more direct approach would be to use Chrome’s Developer Tools to specifically hunt for the gsScrollPos cookie and delete every occurence associated with YouTube. Going down this avenue will enable you to leave the other YouTube related cookies unaffected.

Here’s a quick guide on deleting the gsScrollPos cookie via Developer tools:

Even if you managed to resolve the issue, keep in mind that you are very likely to experience the same behavior again if you will continue using The Great Suspender extension. One solution to take care of the problem indefinitely is to disable the extension for good.

However, if you are fond of using The Great Suspender to automatically suspend unused tabs, you can make use of another Chrome extension such as Edit This Cookie to block the usage o the gsScrollPos cookie permanently.

Код ошибки 400 на YouTube на Android и Windows

Код ошибки 400 с сообщением, что имеются проблема с сетью, появляется на телефоне или планшете Android при попытке открыть Ютуб через приложение. Также, ошибка 400 появляется в браузере при входе на сайт YouTube через компьютер или ноутбук с Windows 11/10 с комментированием «Bad Request» или «Client has issued a malformed or illegal request«

Код 400 говорит, что с вашего телефона или компьютера был отправлен неверный запрос на севера YouTube, и сервер не смог его обработать. Виновником ошибки 400 являются поврежденные файлы cookie в браузере, которые могут неправильно кэшироваться. Также, это могут быть установленные расширения в браузере, как The Great Suspender, которое использует совместные cookie, и при превышении лимита размера файла, появляется код ошибки 400.

В этой инструкции о том, как исправить ошибку 400 на Android и Windows 11/10 в браузере при заходе на сайт YouTube. Зная, как её устранить, вы сможете самостоятельно решать проблемы и c другими сайтами.

Исправить ошибку 404 на телефоне Android

Если проблема с сетью. Код ошибки: 400, появляется на телефоне Android, то откройте «Параметры» > «Приложения» > «YouTube» и нажмите очистить кэш и сброс.

Далее перейдите в магазин приложений Google Play и удостоверьтесь, что вы авторизованы под учетной записью. В Google Play найдите приложение YouTube и обновите его.

Исправить ошибку 404 на компьютере Windows 11/10

Если вы получаете ошибку 404 с пояснением «Bad Request» или «Client has issued a malformed or illegal request» на компьютере с Windows 11/10, то проделайте ниже способы решения.

1. Удалить cookie YouTube

Откройте браузер Яндекс, Edge или Chrome и вставьте в адресную строку следующий адрес chrome://settings/siteData, после чего нажмите Enter. Далее в правом верхнем углу в поиске напишите слово YouTube и нажмите на «Удалить все показанные файлы cookie«.

Примечание: На мобильных телефонах, вы можете попробовать удалить полностью все cookie и историю в параметрах браузера.

2. Удалить gsScrollPos через рефреш

При открытом YouTube и ошибке 400 в браузере, нажмите сочетание кнопок Ctrl+Shift+i, чтобы открыть консоль разработчика. Сверху нажмите на >> и выберите «Application«. Далее в столбце найдите и разверните список «Cookies«, после чего вы должны удалить все файлы, которые начинаются на gs. Просто нажимайте правой кнопкой мыши по ссылке и «Clear«.

Дополнительно

Если ошибка 400 появится вновь, то виновником будет установленное расширение в браузере. В этом случае, вы можете отключать по одному расширению, чтобы выявить виновника. Не забывайте чистить историю и cookie в параметрах браузера, после удаления или отключения расширения.

Также, не забывайте про синхронизацию аккаунта с браузером, ведь старая история может появиться вновь, в зависимости у кого как настроено. В этом случае, почистите историю и cookie, если нужно удалите расширения, сделайте синхронизацию в параметрах браузера или подождите минут 10, потом войдите из аккаунта в браузера. Если ошибка не будет появляться, то можете войти обратно в свой аккаунт.

Fix: YouTube Error 400 in Chrome Your client has issued a malformed or illegal request

YouTube Error 400 in Chrome is not a widespread issue but there are users who get this. The problem occurs every time when people attempt to access any video on this site. Experts say that the cause of the problem is not the operating system. They tried another browser Slimjet and YouTube videos played perfectly without any error messages. So, you need to perform some deep cleaning in Chrome to get rid of this trouble.

How to Fix YouTube Error 400 in Chrome Your client has issued a malformed or illegal request

The entire message that Chrome displays while trying to play videos on YouTube goes like this –

«400. That’s an error.
Your client has issued a malformed or illegal request. That’s all we know».

This resolution process is too simple rather and basically all about clearing cookies from YouTube.

Method 1

Step-1: Launch the Chrome browser from your PC and type the following in address bar.

Step-2: Pressing the Enter button guides you to a new page where you need to search for YouTube by going deep downward.

Step-3: Now, click REMOVE ALL SHOWN button.

Step-4: Clear site data dialog pops-up on the screen. Click Clear All button to bypass the YouTube Error 400 in Chrome.

Give a shot and try to play a video, you should not receive any error. There is another procedure that can help you to clear out all the cookies of this video-sharing site.

Method 2

Step-1: Click on the 3 dots located beside the address bar after opening Chrome browser. Reach out to Settings and click it.

Step-2: Upon opening a new tab, scroll down and click Advanced where the page gets elongated with more options.

Step-3: Locate Content settings and hit a click on it. This instantly takes you to the Content settings page.

Step-4: Here, click Cookies, the first option. Now click the section namely See all cookies and site data (see screenshot).

Step-5: On the following page, there is a search box at the top right corner, type YouTube, and press Enter key.

Step-6: When the cookie entries appear on the screen, click “REMOVE ALL SHOWN” button. Or, delete them all one by one by clicking on the delete icon located on their rightmost.

Hopefully, YouTube should be running smoothly from now onwards.

YouTube is so important nowadays not only for entertainment but also for kind of research activities. Every now and then users need to surf too many videos. In recent days, this strange YouTube error 400 in Chrome is buckling up to restrict the users from watching videos on this site.

Users reported that usually after having a busy session with YouTube when they took a break, they came across YouTube error 400 in Chrome while resuming another session.

A number of people tried some methods like restarting the Chrome browser after closing all tabs and clearing cache but all went into the vein. We have come up with an effective solution for this one.

Conclusion

YouTube is one of the major sources of entertainment at present. So many users use this for research purposes too. Any error that restricts the users from doing these reduces productivity in the end. You can’t afford to happen this. The resolution process to fix YouTube error 400 in Chrome is rather easiest one to put into action. Try out this solution and write to us if you have some more tips to solve this.

BigQuery: Your client has issued a malformed or illegal request, That’s all we know #2855

Comments

deankarn commented Sep 14, 2020

Client

Environment

Go Environment

$ go version
go version go1.15.1

Code

Expected behavior
To succeed or return a useful error

Actual behavior

A cryptic error with absolutely no details is returned:

Your client has issued a malformed or illegal request. «>

Additional context

This code runs as a worker service which builds up rows to load into BigQuery and call Put on the client. We sometimes receive the above error.

As of yet we have not been able to reproduce the error to determine if any data is causing this, but also expected the error response to indicate what the issue might.

The text was updated successfully, but these errors were encountered:

shollyman commented Sep 15, 2020

This one’s likely to be based on your specific project’s behavior and traffic, so the likely outcome here is you’ll need to work through another avenue such as a support or the public issue tracker. They’ll have access to see more details about your specific projects. That said, we can try to isolate some more details.

What order of QPS are we talking about here? What’s the batch factor involved (how many rows per Put call)?

You mention you build up rows, which I’m interpreting to mean you are queuing data in some fashion before sending. Do you happen to flush it based on a specific condition shared by multiple workers, like a specific deadline time? I’ve observed things like this where a large number of senders happen to all transmit in lockstep, with insufficient jitter among them.

deankarn commented Sep 15, 2020

We have about 30 services reading from a Kafka queue(one for each partition) which:

The Put’s/s are somewhere around 30 rows, 3 Put’s/s. FWIW these rows are fairly large and why the limit is 10 to not go over the 1MB streaming insert limit. The total across all services is around 100 rows, 90 Put’s/s.

Each service runs the code synchronously and so the client is not shared amongst multiple goroutines.

shollyman commented Sep 15, 2020

Thanks for helping explain the data shape a bit more. That level of traffic does not seem problematic and excludes some of the high volume scenarios I was originally considering.

How frequently are you encountering these errors? Have you captured a corresponding request that triggered such a response?

deankarn commented Sep 18, 2020

@shollyman I have not had the chance to capture the payload yet due to other competing priorities, however, it is happening on the order of hundreds of times per day.

deankarn commented Oct 2, 2020

@shollyman I was finally able to capture a payload which causes the issue and was able to reproduce.

It was a payload containing 10 messages. After digging into the messages themselves there was nothing special about them.

So the payload if obviously too large but the incorrect error is being returned. I dug into the code which led me into https://github.com/googleapis/google-api-go-client/tree/master/bigquery/v2 but I was unable to find any offending code.

I suspect somewhere server-side there is an issue. Perhaps limiting the number of bytes read off the posted body is causing it to be cut short and cause a malformed error rather than returning the correct payload too large error? I’ve seen this sort of thing, assuming the backend servers are written in Go, when using the http.MaxBytesReader which does not allow capturing of the error in a nice way.

Unfortunately I cannot share the payload as it contains sensitive data. But I hope this gives enough guidance to look into it further on your end.

Your client has issued a malformed or illegal request that s all we know

Je pense que vous allez trouver les liens suivants utiles:

•Votez! Appel à la contribution. Nous vous prions de considérer que dans le cadre de ce forum on n’offre pas de support technique et aucune garantie de la part de Microsoft ne peut être offerte.

tous d’abord merçi de m’avoir repondu.

j’ai deja effectuer toute les manip dans les liens proposer,sans resultat.

Si je puis me permettre, il suffit de donner le lien du site que vous cherchez à traduire dans Google traduction pour que celui ci traduise dans la langue que vous souhaitez la page en question.

Vers l’infini et au delà

» il suffit de donner le lien du site». c’est a dire?

dans ma recherche google systematiquement les liens ou c’est noté traduire la page ne sont pas accessible,j’ai automatiquement l’erreur 400.

et ceux sur toutes les traductions.

merçi et bonne journée.

Vous vous trouvez donc sur IE, quand vous êtes sur Google et que vous souhaitez traduire une page il vous affiche erreur 400.

Avez vous le même problème avec d’autres navigateur?

Si vous passez par Google traduction et que vous collez l’adresse en question dans l’encart prévu, que vous choisissez la langue d’import et celle d’export et que vous cliquez dans l’encart à gauche avec le lien que sort Google.