Menu
Reply
Highlighted
  • 72
  • 2
  • 16
Dialled in
1,086 Views
Message 1 of 7
Flag for a moderator

HTTP Error 400

My apologies if this has been highlighted recently, I did check but found most of other threads about problems with accessing email accounts.

The above subject title is what I get when using the same email link to get into my email account that I used for some time and don't even reach the log in stage before that message comes up. I'm having no issue with accessing other VM stuff or any other website, and this has only occurred this morning.

It says if the error continues, to let the page owner know. The error has continue so I'm letting you VM know.

Cheers Smiley Happy

0 Kudos
Reply
Highlighted
  • 12.62K
  • 1.68K
  • 5.63K
Very Insightful Person
Very Insightful Person
1,074 Views
Message 2 of 7
Flag for a moderator

Re: HTTP Error 400

You need to tell them what the link (url) that you are having the problem with is.  Otherwise how are they able to check it?

Edited to add:  The correct link to use is:  https://mail2.virginmedia.com/

_________________________________________________________
Graham
I am a VM customer. There are no guarantees that my advice will work.

As a Very Insightful Person, I'm here to share my knowledge. I don't work for Virgin Media.

Click to learn more about VIP

Use Kudos to say thanks

 

Mark as Helpful Answer if I've helped

0 Kudos
Reply
Highlighted
  • 72
  • 2
  • 16
Dialled in
1,058 Views
Message 3 of 7
Flag for a moderator

Re: HTTP Error 400

Thanks Graham. That's the very same link that is at the very top of this page and on the home page. It's the only one I know of, that's why I didn't put it in my post.

I just clicked on that link and it's now saying: "Connection error. The service is not avaialble right now. Retry".

Edited to add: I just clicked on 'Retry' and got the same message as before:: 

"This page isn’t working

If the problem continues, contact the site owner.

HTTP ERROR 400"
 
0 Kudos
Reply
Highlighted
  • 12.62K
  • 1.68K
  • 5.63K
Very Insightful Person
Very Insightful Person
1,049 Views
Message 4 of 7
Flag for a moderator
Helpful Answer

Re: HTTP Error 400

Can you try clearing your browser cache or try using a different browser?  Your symptoms suggest a local issue as the page the link directs to is working correctly.

_________________________________________________________
Graham
I am a VM customer. There are no guarantees that my advice will work.

As a Very Insightful Person, I'm here to share my knowledge. I don't work for Virgin Media.

Click to learn more about VIP

Use Kudos to say thanks

 

Mark as Helpful Answer if I've helped

Highlighted
  • 72
  • 2
  • 16
Dialled in
1,039 Views
Message 5 of 7
Flag for a moderator

Re: HTTP Error 400

Thanks again. Weirdly I've just tried the link again and I got as far as the log-in page this time. But when I log in, I get the same sequence as in my previous email. The response I get seems to change every couple hours without me moving cookies, etc.

As advised I also tried the link in IE (i've been using Chrome) and it took a little longer but was able to get through to me inbox. Smiley Surprised

0 Kudos
Reply
Highlighted
  • 1.52K
  • 187
  • 853
Very Insightful Person
Very Insightful Person
1,029 Views
Message 6 of 7
Flag for a moderator

Re: HTTP Error 400

Why do I need to "clear cache and cookies?" in my browser.

Why do we ask you to do this? -

To deal with issues like “Forbidden” or getting stuck in a never ending loop of “robot” or “three dotsor HTTP errors when accessing Virgin Media (web)Mail.

One of the most frequent steps in problem resolution is to clear the cache and cookies from the browser. It’s understandable why this might come over as only a slightly more technical version of "have you tried turning it off and back on again?" - but it isn't! It's actually an important first step for almost any troubleshooting procedure.

The Cache

This is a tool used by your internet browser to speed up the page loading process. Any element that appears on multiple pages within a single site - for instance, the image file representing a site's logo - will be placed in the browser's cache. This is really just a local folder on your hard drive that stores a copy of frequently-accessed page resources. Because it's faster to load an image from your hard drive than it is to download it from a remote server, the browser just goes back to the cache every time it needs to display the logo when you surf to a new page. This saves not only the time needed to download the image file, but it also conserves network bandwidth. Caches are a very effective way to make browsing the web faster, more convenient and less aggravating.

Cookies

These are also files which are saved on your hard drive. Instead of representing content that's displayed on a website though, they represent settings selected by the individual person who's using the browser. For instance, if a user browses to a website, signs into their account, and selects the "remember me" option, then the next time the user visits that site, they won't have to type in their username - the site will 'remember' it because the user's preference to do so was written into a 'cookie' file that was saved on their computer's hard drive. Any time a site asks a user to select preferences, there's a good chance those preferences will be saved in a cookie.

The Wikipedia definition says -

Cookies are arbitrary pieces of data, usually chosen and first sent by the web server, and stored on the client computer by the web browser. The browser then sends them back to the server with every request, introducing states (memory of previous events) into otherwise stateless HTTP transactions. Without cookies, each retrieval of a web page or component of a web page would be an isolated event, largely unrelated to all other page views made by the user on the website. Although cookies are usually set by the web server, they can also be set by the client using a scripting language such as Javascript (unless the cookie's HttpOnly flag is set, in which case the cookie cannot be modified by scripting languages).

The cookie specifications require that browsers meet the following requirements in order to support cookies:

  • Can support cookies as large as 4,096 bytes in size.

  • Can support at least 50 cookies per domain (i.e. per website).

  • Can support at least 3,000 cookies in total.

So why is it sometimes a problem to keep the cache and cookies around? Because sites change and develop over time. When a site is updated, the files saved in the cache may conflict with what's actually coded into the website. As a very simplified example, consider a file called "VM-logo.jpg" in the cache. Obviously it will represent the logo for the website - VM in this case - but what happens if the website undergoes a redesign? The NEW logo is also saved to the site with the file name "VM-logo.jpg," but since the original version of "VM-logo.jpg" is already stored on the user's cache, the browser may not be able to tell the difference. It could very well detect that the site calls for "VM-logo.jpg" and return the cached version of the OLD image instead of the new one downloaded from the server. Similarly, data that's stored in a cookie can rapidly become outdated when a site is modified. If the site changes the location of a piece of data within a cookie, retrieving data from “Field 5” may produce the wrong answer if it picks it up from an old cookie (and I know that website coders should check the version of the cookie first – but many of them do not). If your browser can store up to 3000 cookies, including multiple versions of the cookies from your most-frequently-accessed sites, it’s easy to see how the wrong version of a cookie can be picked up.

Depending on what files are stored in the cache for a given website, caching errors can be fairly broad in scope. If a logo file is cached, the error could be limited to simply displaying outdated content. But if one of the files that controls “how the website operates” is cached, then the end user can see some unexpected, strange behavior. The length of time that a file remains in the cache varies; some browsers have controls allowing users to dictate how long cached files are kept around before the browser decides they're outdated and need to be refreshed.

Having a user clear their cache and cookies when we are troubleshooting an issue is a way to ensure that we're seeing the same version of a website as the person we're working with, rather than the version modified by a multitude of different cookies lying around in the user’s cookies folder.

How do you clear your cache and cookies? Instructions for individual browsers all differ so Google them thus – “Clear xxx browser cache and cookies”.

If anybody claims - “I haven’t changed anything since date X”, they are almost certainly mistaken because if they have logged into practically ANY website since date X, then at the very least they will have picked up a new cookie or two.

The Full Monty

(a) clear your browser’s cache and cookies of everything which mentions Virgin. If you find that difficult just clear ALL cache and cookies.

(b) delete any or ALL bookmarks which you are using for VM mail.

(c) close down your browser completely after doing all this.

(d) re-open the browser and go to www.virginmedia.com and click on the email link in the black band at the top of the page. That should take you to the sign-in screen.

(e) If all that doesn’t work, try using a different browser, or use an e-mail client.

 

Highlighted
  • 72
  • 2
  • 16
Dialled in
1,002 Views
Message 7 of 7
Flag for a moderator

Re: HTTP Error 400

Thanks for the interesting info Bill. I had cleared some cache and cookies this morning and was able to access my inbox from my usual browser.