Contact Us Anytime:
Http Caching
Your users will get more loyal and your revenue will increase with a super-fast site.
Benefits Features
alt_picture! Global reach with no big investments With JoDiHost's help you'll get access to the world's best edge network with no need to build the one and without big investments.
alt_picture! Guaranteed performance and delivery Your applications and content are guaranteed to be delivered by our cutting-edge storage and caching infrastructure.
alt_picture! Make it your own Our CDN is optimized for every type of content delivery, so you can have any e-commerce website or a streaming video destination.
alt_picture! Totally satisfied customers It doesn't matter where an end user is located for our ultra-fast global delivery. Because content is always delivered from the server that is fastest for each user with our intelligent global load balancing.
alt_picture! Search engine optimization Nowadays to get high ranking in major search engines a website must perform as fast as possible. With Jodihost's speed you website's rankings, traffic and revenue can be greatly increased.
alt_picture! Solid infrastructure You can be sure that your content is stored securely and flexibly across the globe with our cutting-edge hardware paired with the best content delivery software in the industry.
alt_picture! Massive Scale Don't worry about host capacity and scale quickly to accommodate flash crowds or other surges in demand.
alt_picture! Intelligent Platform In order to get maximum performance small files are served from RAM and large files from disk.
alt_picture! Flexible Origin Server Options Store content with JodiHost or on your own hardware and cache automatically as needed.
alt_picture! Powerful Security Prevent any form of content theft, hotlinking and piracy with robust security features. Deploy custom SSL certificates quickly and easily.
alt_picture! Manage Your Downloads We offer Download Manager to deliver globally-cached files to your clients in an intelligent, interactive and flexible way.
alt_picture! Super-Fast Global Load Balancing There is no waste of time in deciding where to serve content from with one of the fastest DNS infrastructures in the world.
alt_picture! Web Based Control Panel You can log in from anywhere in the world and manage your content with our user-friendly, browser-based Media Control Center.
alt_picture! The Industry's Best Analytics You can better understand your audience with our EC360 Analytics Suite that gives you detailed visibility and thus you can optimize the user experience.
alt_picture! Make Your Own Rules With our powerful HTTP Rules Engine you have the whole control over when, how and if the content is served and delivered.
alt_picture! All-day Support You can always rely on our support. Anytime, day-and-night we are ready to help you with any question with all the patience and without delays.
Try our features with a no commitment test account


Our CDN Network is able to transmit the customer’s content in a more efficient manner to his users via serving that content through the HTTP Large platform and achieving maximum productivity. The network has been optimized to allow data to quickly move between where it is stored and the point-of-presence (POP) closest to the user that requested it. At the same time a copy of the requested content may be stored on that POP. This process is known as caching. Once content has been cached, all future requests for that content from that region can be delivered directly from that POP. This removes the need to retrieve the data from the origin server. The following diagram demonstrates how content is delivered via the CDN to a user.

HTTP Caching
CDN Data Delivery

1. This data delivery process starts with a user's request for content. This request is directed to the POP closest to the user.

2. An edge server in that POP will check whether the requested content has been previously cached.

3. The requested asset is delivered via the POP from step 1 to the use that requested it.

4. The requested asset may then be cached on the POP that received and fulfilled the request. This allows that POP to immediately fulfill future requests for that asset without having to forward the request to the origin server.

There are two types of caching that can take place when an asset is routed through our CDN, which are edge server and user agent (e.g., web browser) caching. Edge server caching determines whether the requested asset will be cached for a particular POP and for how long. This type of caching determines when an edge server on that POP will check for a new version from the origin server. User agent caching determines whether the requested asset will be cached on a web browser and for how long. By default, this type of caching determines when a user agent (e.g., browser) will revalidate the cached asset with the edge server.

If an asset’s headers do not prohibit caching, then the default behavior is to cache it on our POPs and on each user agent (e.g., web browser) that requests it according to the asset's Cache-Control and Expires header information. If an asset does not have header information, then it will be assigned a TTL of 7 days (i.e., Cache-Control: max-age=604800) when it is cached on our edge servers and by the user agents that requested it. The customer can override this default behavior by manually caching and purging assets from our POPs or through the use of HTTP Rules Engine.

Once the asset has been cached on a POP, all future requests that originate from the region served by that POP will be served directly from that POP while the asset is fresh. Once the asset’s TTL has expired, then an edge server from that POP will revalidate the asset with the origin server. If the asset has not been modified, then the header information for the cached asset on the edge server and the user agent that requested it will be updated. Otherwise, a new version of the asset will be retrieved and cached on the edge server and the user agent.

If a user requests an asset that has not been previously cached on the corresponding POP, then an edge server will retrieve it from the origin server. The entire asset will then be cached on that edge server provided that its headers do not prohibit caching, regardless of whether the user performed an HTTP range request or aborted their download. By automatically retrieving and caching the entire asset, future requests for that asset will not require an edge server on that POP to download it again from the customer’s origin server while the asset is still fresh. This functionality reduces the load on the origin server and allows future requests to be served from cache. This ensures the speedy delivery of the customer’s content to his users.

By default, an asset is not cached on our edge servers until it is requested by a user. This means that the first user in a particular region to request an asset will cause the corresponding edge server to request it from the origin server. After which, the asset will remain cached on that edge server until it is automatically or manually purged. Therefore, the first user to request a particular asset will take slightly longer to retrieve it than all other subsequent customers. If the customer has a large event or content that becomes simultaneously available to a large volume of end-users (e.g., a new movie release), then it might be helpful to load all media content on our edge servers.

Requests that contain a query string can be cached differently. The customer can choose to cache these types of assets in one of three different ways. Each cache method is explained below.

Cache Method
This is the default mode for handling URLs that contain query strings (e.g., Asset.txt?Data=True). This mode will ignore query strings in the URL. It will only cache a single asset per URL, regardless of the presence of query strings. However, if there is a cache miss or an expired cache asset needs to be revalidated, then the full CDN URL, including query strings, will be passed to the customer origin server.
This mode prevents requests containing query strings from being cached. All requests that contain query strings will be forwarded to the customer origin server.
This mode will cache an asset for each request made with a unique URL. A unique cache asset will be created by even the slightest variation in the query string. It is recommended that you enable the query string logging feature when taking advantage of unique-cache mode. Additionally, it is highly recommended that this mode be avoided when requests will contain query strings that will result in a very low cache hit ratio. For example, information such as session ID or user name would create such a scenario.

By default, no-cache or unique-cache mode cannot be used with Token-Based Authentication. This means that if the customer has protected at least one folder with Token-Based Authentication, then the only cache method that will be available from the MCC is standard-cache. Likewise, if he has configured query string caching to use no-cache or unique-cache mode, then he will not be allowed to protect a folder with Token-Based Authentication.

Another way to override the default cache behavior is to overwrite the cache headers assigned to the customer’s assets. This can be accomplished through HTTP Rules Engine. This feature allows the customer to create custom rules that can be used to handle how our edge servers cache and grant access to assets requested through HTTP-based platforms.

Try our features with a no commitment test account
Application Delivery Accelerate delivery of web applications and non-static content.
Caching Our delivery and acceleration services will lead you to the world's digital threshold, from complete websites to mobile.
Analytics Full and instant visibility into performance of the content and the user experience.
Download Manager Your files are delivered globally with super-fast speed, intelligence and flexibility.
Security Protect your applications and content from unauthorized use with the powerful security tools.
Edge Optimizer Powered by Google PageSpeed, Edge Optimizer keeps your application's data and logic off of your network.
Streaming We will deliver better than anyone else your Flash, Silverlight, or HTTP – live or on-demand.
Storage It is more than just CDN storage. Security, replication, and caching infrastructures really mean massive scale at ultra-fast rates of speed.
Rules Engine With our powerful tool you have the whole control over when, how and if the content is served and delivered.
Piranha Purge Better caching flexibility, efficiency, and performance with Piranha Purge.

High-performance CDN solutions are costly?NOT ANYMORE!

Unprecedented INXY promo will get
you Premium-class CDN

for as low as $10/TB!contact us now

Premium-class CDN solution has never been cheaper!

Unprecedented Promo
will get you CDN from

for as low as $6/TB!contact us now