I think this might be something wrong with the Javascript or CSS.  There
should be a tab that displays that message, but you shouldn't see the tab --
instead when you view source it'll load the source code asynchronously and
show the tab.  If JS or CSS didn't load, it might all display in a funky
way.
You could look at the source and check those JS and CSS links to make sure
they are working, or maybe they give a useful error message.


On Fri, Jul 10, 2009 at 6:12 AM, durumdara <[email protected]> wrote:

>
> Hi!
>
> I used Pylons under apache (with proxy).
>
> Interesting, when I use mod_rewrite with proxy (A), the Error page is
> normal.
>
> When I not use mod_rewrite, only proxypass (B), the Error page is
> minimal and hardly readable.
> In this case Pylons said: "There is no source code to display"...
>
> What happened? What is the different?
>
> A.) Good, but I have not change to set "retry" param of proxy.
> ProxyPreserveHost On
> TimeOut 600
> ProxyTimeout 600
>
> RewriteEngine On
> RewriteCond %{REQUEST_URI} !^/img/.*
> RewriteCond %{REQUEST_URI} !^/error/.*
> RewriteCond %{REQUEST_URI} !^/media/.*
> RewriteCond %{REQUEST_URI} !^/css/.*
> RewriteRule ^/(.*) http://127.0.0.1:10020/$1 [L,P]
>
> B.) With retry - but error page changed to very simple view....
> ProxyPreserveHost On
> TimeOut 600
> ProxyTimeout 600
>
> ProxyPassMatch "/(img|error|media|css)/" !
> ProxyPass / http://127.0.0.1:10020/ retry=120 timeout=600
> ProxyPassReverse / http://127.0.0.1:10020/
>
> So, what is the different?
>
> Thanks for your help:
>  dd
> >
>


-- 
Ian Bicking  |  http://blog.ianbicking.org  |
http://topplabs.org/civichacker

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pylons-discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/pylons-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to