Oops. Sorry, it was Barry suggesting DNS change.

On Saturday, April 28, 2012 10:13:26 AM UTC+2, alex wrote:
>
> I think you can actually do it without manual intervention from Google 
> internally:
>
> Let's say your app (with cached blank page) is currently accessible as 
> www.example.org
>
> 1. make sure you remove "cache-control: public ..." headers from the 
> response
> 2. add a mapping that will make your app accessible as app.example.org
> 3. like Joshua suggested, change www CNAME into www A DNS record pointing 
> somewhere else, where you do a simple (maybe even permanent) redirect to 
> app.example.org
>
> Even though it seems like your blank page is cached for a long time now, 
> www DNS record will expire sooner (normally 24 ours if you haven't changed 
> TTL)
>
> Hope that helps.
>
> On Friday, April 27, 2012 10:31:47 PM UTC+2, Joshua Smith wrote:
>>
>> Let's review:
>>
>> Google has cached a blank version of your / page.
>>
>> The blank page is only about 12 hours old. The max-age is set to 1 year. 
>> So this problem will go away on its own in a year.
>>
>> It really sucks to be you right now. :(
>>
>> You should try really, really hard to figure out how this happened. I've 
>> never heard of anything like this on these lists, so it's likely that it's 
>> a bug in your code someplace that can yield blank page with a 1 year 
>> timeout.
>>
>> If you repeat that telnet session, you can probably figure out more 
>> exactly when the page was cached, then you can look at your logs to figure 
>> out what caused it. Maybe.
>>
>> Getting the problem cleared would require some manual intervention from 
>> google. They'd have to manually invalidate that cache entry. I'd bet money 
>> that the Google App Engine team has no ability whatever to cause that to 
>> happen. Upgrade to a $500/month enterprise account perhaps?
>>
>> I've been trying to think of a way to fix this using DNS, but I'm coming 
>> up empty, short of changing your domain name.
>>
>> -Joshua
>>
>> On Apr 27, 2012, at 3:53 PM, Gregory Nicholas wrote:
>>
>> yep.. bingo.. what are my options from here?
>>
>>
>>
>> On Fri, Apr 27, 2012 at 12:29 PM, Joshua Smith 
>> <joshuaesm...@charter.net>wrote:
>>
>>> You could test this theory by hitting /?foo
>>>
>>> On Apr 27, 2012, at 3:17 PM, Matthew Blain wrote:
>>>
>>> > Typically a 204 with nothing run is simply a signal that your content
>>> > has been cached elsewhere in Google's network. If you responded with
>>> > cache-control: public with a max-age of something, it may be cached
>>> > until that expires.
>>> > Without futher info (such as an appid or the domain), it's hard to
>>> > tell what's going on.
>>> >
>>> > On Apr 27, 11:34 am, Gregory Nicholas <faction.greg...@gmail.com>
>>> > wrote:
>>> >> really need help.. i'm at a place where i can't really fix this on my 
>>> own..
>>> >> it's 11:00am.. been trouble shooting this since 9pm last night (thank 
>>> god
>>> >> for adderall)
>>> >>
>>> >> *Preface (kinda):*
>>> >>
>>> >>    - we've been working with appengine for a couple years now 
>>> (haven't seen
>>> >>    everything, but been through a lot of troubleshooting)
>>> >>    - python 2.7, webapp 2.3, django 1.2, HRD
>>> >>    - absolutely NO issues with local dev environ, production issue 
>>> only
>>> >>
>>> >> *Issue / Symptoms:*
>>> >>
>>> >>    - only the main url path: "/" for my app domain is not serving the
>>> >>    request to my app
>>> >>    - essentially breaks down to only the home page not working on
>>> >>    http://www.<domainname>.com
>>> >>    - the main url path for the appspot
>>> >>    domain: http://<domainname>.appspot.com serves
>>> >>       - request is routed properly from the app.yaml to my request 
>>> handler
>>> >>    - on http://<domainname>.com, any request to a subpath STILL WORKS!
>>> >>       - ex: http://< domainname >.com/user/login serves, works
>>> >>    - the request IS hitting my application:
>>> >>       - attached is a screen shot of my app logs, where the main path 
>>> serves
>>> >>          - not hitting my app.yaml file, and not routed to any request
>>> >>          handlers
>>> >>          - appears as though my code is never being executed for the 
>>> request
>>> >>
>>> >> *What I've tried:*
>>> >>
>>> >>    - i telnet'ed and tracerouted the domain name to rule out it being 
>>> a DNS
>>> >>    issue
>>> >>       - see attached terminal screenshot
>>> >>    - i've redeployed my app several times
>>> >>    - i reverted the default version to a previous version
>>> >>    - i've shutdown any instances several times
>>> >>    - i switched from automatic instance allocation to manual, 
>>> switching
>>> >>    from F1 to F2 classes
>>> >>
>>> >> PLEASE HELP!!!
>>> >>
>>> >>  Screen Shot 2012-04-27 at 11.14.15 AM.png
>>> >> 193KViewDownload
>>> >>
>>> >>  Screen Shot 2012-04-27 at 11.31.23 AM.png
>>> >> 156KViewDownload
>>> >
>>> > --
>>> > You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> > To post to this group, send email to google-appengine@googlegroups.com
>>> .
>>> > To unsubscribe from this group, send email to 
>>> google-appengine+unsubscr...@googlegroups.com.
>>> > For more options, visit this group at 
>>> http://groups.google.com/group/google-appengine?hl=en.
>>> >
>>>
>>> --
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To post to this group, send email to google-appengine@googlegroups.com.
>>> To unsubscribe from this group, send email to 
>>> google-appengine+unsubscr...@googlegroups.com.
>>> For more options, visit this group at 
>>> http://groups.google.com/group/google-appengine?hl=en.
>>>
>>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To post to this group, send email to google-appengine@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> google-appengine+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/google-appengine?hl=en.
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-appengine/-/I-L34Ak9d5QJ.
To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to