Show search and navigation.

 

Testing Data Delivery from a Specific POP

Applies To:
HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.
HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.
ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

By default, a request for CDN content will be directed to the POP closest to the client. This behavior ensures that the optimal path is used to deliver content to your users. However, your organization may require that you validate that one or more specific POPs can deliver your content. This can be accomplished by modifying the hostname used to request your content as indicated below.

Platform Domain Example

HTTP Large

POP1.wpc.edgecastcdn.net

oxr1.wpc.edgecastcdn.net

HTTP Small

POP1.wac.edgecastcdn.net

mib1.wac.edgecastcdn.net

ADN

POP1.adn.edgecastcdn.net

mex1.adn.edgecastcdn.net

The term POP should be replaced by the three-letter abbreviation for the POP to which the request will be directed. View a list of our POPs.

The above hostnames should not be used for production traffic. This type of setup will adversely impact overall web page load times.

Viewing Response Header Data

The following sample requests will return header data upon requesting content from our HTTP Large servers in New York.

Wget:

wget -SO Response.txt nya1.wpc.edgecastcdn.net/00FC48F/demo.jpg

cURL:

curl -s -D - nya1.wpc.edgecastcdn.net/00FC48F/demo.jpg -o /dev/null
More Information