Forum Discussion
Solved
Cannot add image to Header in Excel - Bad Request error
I have two users getting the same error in Excel. The error says bad request too long. In the past I could have the user select Bing then work offline. But we do not get any options. Everything I fin...
Another solution I found if you are working on the desktop app is to go into File>Options>General>Privacy Settings>and unclick turn on optional connected experiences. Once you get the picture in, you can turn it back on but you do have to restart office for each. I am teaching Excel and both one of my students and I had the same problem so it may be fairly common.
I see. No, I did not change places. I work from home.
In the computer Settings > Apps > Default Apps find Chrome or Microsoft Edge. In the page that opens with a list of applications, scroll down and find HTTP. Change that from one to another and change back after a while.
I have a really low knowledge about internet language, but, I was reading that the request header used in HTTP protocols triggers a response. If the request header is faulty, the response does not happen. It can become faulty by different reasons, like caches. That is why I think that when I set HTTP to be managed by Microsoft Edge then I changed back to Chrome, I actually cleared Chrome "fault". There was something wrong with Chrome managing HTTP protocols. Anyway. Have a try. Hope it helps.
In the computer Settings > Apps > Default Apps find Chrome or Microsoft Edge. In the page that opens with a list of applications, scroll down and find HTTP. Change that from one to another and change back after a while.
I have a really low knowledge about internet language, but, I was reading that the request header used in HTTP protocols triggers a response. If the request header is faulty, the response does not happen. It can become faulty by different reasons, like caches. That is why I think that when I set HTTP to be managed by Microsoft Edge then I changed back to Chrome, I actually cleared Chrome "fault". There was something wrong with Chrome managing HTTP protocols. Anyway. Have a try. Hope it helps.
Thanks for the walk through. I finally heard back from Microsoft and they recommended the same thing. My users default and HTTP were set to Edge. So I changed it to chrome and sadly it did not work. Then I tried changing them back to Edge and it still did not work. Now I have them both set to chrome and we are going to give it time then change it back to Edge like you did the first time it fixed the issue for you. I will update this if that works or not.
