MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
WebPagetest Forums - Location from getLocations is "invalid"?

WebPagetest Forums

Full Version: Location from getLocations is "invalid"?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Hi,

I am trying to test several websites with different locations, and the page is giving me the following error message:
> Invalid Location, please try submitting your test request again.

- The location I found is listed under the page,
http://www.webpagetest.org/getLocations.php
- I have the API key issued to myself.

The example is the following (with google.com given for the url):
http://www.webpagetest.org/runtest.php?l...XXXXXXXXXX

As you can see, the location is Chicago:IE10 and it is (at the time I am posting this thread) appearing on the getLocations page.

Is there a solution to this problem?
The location for IE10 in Chicago should be Chicago_IE10
(05-30-2015 06:54 AM)andydavies Wrote: [ -> ]The location for IE10 in Chicago should be Chicago_IE10

Thanks for the quick reply.

I tried Chicago_IE10 and it gives me the result of running from Dulles, VA - Chrome - Cable, which is the default value as stated in the RESTful APIs page.

Here is the list of locations I would like to test from (names copied from getLocations page's Location column):
  • Dulles:Chrome
  • Chicago_IE10
  • LosAngeles:Chrome
  • Singapore_IE8
  • Seoul:Chrome
  • Tokyo

Does anyone have insight regarding this? Simply putting the above location for runtest.php's parameters do not work, all of them keep returning the test results with the Dulles default location.

Cheers,
hunj
Ah yes, only some of the agents are available with the Akamai sponsored API keys.

So if you have one of those keys these will be your choice of locations:

Dulles_IE9
Dulles_IE10
Dulles_IE11
Dulles:Chrome
Dulles:Canary
Dulles:Firefox
Dulles:Firefox Nightly
Dulles:Safari
Dulles_Chrome40
Dulles_MotoG:Motorola G - Chrome
Dulles_MotoG:Motorola G - Chrome Beta
Dulles_MotoG:Motorola G - Chrome Dev
ec2-us-east-1:Chrome
ec2-us-east-1:IE 11
ec2-us-east-1:Firefox
ec2-us-east-1:Safari
ec2-us-west-1:Chrome
ec2-us-west-1:IE 11
ec2-us-west-1:Firefox
ec2-us-west-1:Safari
ec2-us-west-2:Chrome
ec2-us-west-2:IE 11
ec2-us-west-2:Firefox
ec2-us-west-2:Safari
ec2-eu-west-1:Chrome
ec2-eu-west-1:IE 11
ec2-eu-west-1:Firefox
ec2-eu-west-1:Safari
ec2-eu-central-1:Chrome
ec2-eu-central-1:IE 11
ec2-eu-central-1:Firefox
ec2-eu-central-1:Safari
ec2-ap-northeast-1:Chrome
ec2-ap-northeast-1:IE 11
ec2-ap-northeast-1:Firefox
ec2-ap-northeast-1:Safari
ec2-ap-southeast-1:Chrome
ec2-ap-southeast-1:IE 11
ec2-ap-southeast-1:Firefox
ec2-ap-southeast-1:Safari
ec2-ap-southeast-2:Chrome
ec2-ap-southeast-2:IE 11
ec2-ap-southeast-2:Firefox
ec2-ap-southeast-2:Safari
ec2-sa-east-1:Chrome
ec2-sa-east-1:IE 11
ec2-sa-east-1:Firefox
ec2-sa-east-1:Safari
Thanks for your insight.
Seems like the only way for me is to manually run each test on my preferred servers.

Cheers,
hunj
Reference URL's