Pylons and CDN

[Biswas, Pinakee]

Hi,

 

We would like to know if any portal built on Pylons framework is being delivered through CDN today.

 

We have a portal based on Pylons and we are having issues delivering the portal via CDN. The CDN edge servers run regular web servers besides pulling the resources/pages from the actual portal server (and caching them,). But somehow the pages are not showing up properly when delivered via CDN.

 

I know delivering Dynamic pages/resources based on PHP works fine with CDN.

 

We would really appreciate if you could provide us some info on the above. I am not sure if we need to do any specific configuration etc for the portal to work

 

Looking forward to your response and support..

 

Thanks,

Pinakee Biswas

Director & CTO

 

 

7E- Mail: pin...@vvidiacom.com I 8Web: http://www.vvidiacom.com

 

[Jonathan Vanasco]

can you share some urls so we can see?

[Mengu]

That shouldn't be a Pylons problem. How are you uploading static
content or are you uploading at all? Is CDN just following your url?
Do you replace the static content urls with the CDN urls? Can you
provide us some urls?

On Apr 8, 9:15 am, "Biswas, Pinakee" <pina...@vvidiacom.com> wrote:
> Hi,
>
> We would like to know if any portal built on Pylons framework is being
> delivered through CDN today.
>
> We have a portal based on Pylons and we are having issues delivering the
> portal via CDN. The CDN edge servers run regular web servers besides pulling
> the resources/pages from the actual portal server (and caching them,). But
> somehow the pages are not showing up properly when delivered via CDN.
>
> I know delivering Dynamic pages/resources based on PHP works fine with CDN.
>
> We would really appreciate if you could provide us some info on the above. I
> am not sure if we need to do any specific configuration etc for the portal
> to work
>
> Looking forward to your response and support..
>
> Thanks,
>
> Pinakee Biswas
>
> Director & CTO
>

> cid:E95B8D36-1F36-4B11-B91A-CF8977B83894
>
> 7E- Mail:  <mailto:pina...@vvidiacom.com> pina...@vvidiacom.com I 8Web:
> <http://www.vvidiacom.com/>http://www.vvidiacom.com
>
>  image001.jpg
> 15KViewDownload
>
>  image002.png
> < 1KViewDownload

[Biswas, Pinakee]

Hi,

Thanks for your response.

We plan to deliver the whole portal using CDN. We are already delivering the static content (like images, videos) using CDN. The problem comes when we try to deliver the whole portal using CDN.

Following is the snapshot of the configuration:

1. The portal is hosted at ip address IPp (lets say).
2. I create a DNS entry - cdn.example.com with ip as IPp.
3. I configure cdn.example.com in CDN which provides a URL.
4. I add the CDN URL as CNAME in DNS for www.example.com

When I try to access www.example.com, some of the dynamic content doesn't show. Application on pylons is running behind Apache web server. Apache web server acts as a proxy.

I am not sure if we are doing anything wrong.

Would appreciate if we can get some pointers on what the right approach would be and if pylons works well with CDN.

Looking forward to your response and support..

Thanks,
Pinakee Biswas
Director & CTO

FE- Mail: pin...@vvidiacom.com I IWeb: http://www.vvidiacom.com

--
You received this message because you are subscribed to the Google Groups "pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discus...@googlegroups.com.
To post to this group, send email to pylons-...@googlegroups.com.
Visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

[Jonathan Vanasco]

You should look at your HTML source and your Apache logs. This most
likely has nothing to do with Pylons.

You should ensure that you can access the items via the urls that you
are generating ?

My guess is that either:
- your cdn or origin server is configured to respond to (www.)?
example.com , not cdn.example.com
- you're generating a url that isn't pointing to your CDN
- your CDN doesn't have the file , or is configured incorrectly

The standard CDN strategy I've used across every web language/
framework is this :

- preface all "CDN" likely content with a global variable "cdn_root"
- your environment decides what the CDN root is -- an IP address, a
domain name, an empty string (for the same server)
- - src="${cdn_root}/images/logo.gif" could then render as "http://
example.com/images/logo.gif" or "/images/logo.gif"
- i prefer mirrored CDNs , so a request to "http://cdn.example.com/
a.gif" serves a cache version of "http://origin.example.com/a.gif"