Topic: Some pages unavailable.

I'm getting a "Sorry! This page is not available" when I try to:

-Add a new channel (http://www.chumby.com/widgets/new_channel)
-While browsing widgets, "add to channel" (e.g http://www.chumby.com/guide/add/Christmas%20Countdown)

Adding widgets from withing the "newest widget" widget running on the chumby itself DOES work, however.

Am I the only one experiencing this problem?

TIA
   nixkalo

Re: Some pages unavailable.

I'm not seeing the problem - is it still happening for you?

Where are you located?

Anyone else having this problem?

nixkalo - if you're still seeing this on Monday, please contact Customer Service.

Re: Some pages unavailable.

i see all of your hits on those pages in our logs and there are only HTTP status code 200s to accompany them, which indicates
that the page was served OK.

if you continue to have problems, feel free to send me email today [ mike at chumby dot com ] and then contact support
on monday.

/mdkail

Re: Some pages unavailable.

Mike, Duane:First of all, thanks for the quick answer, even during a weekend.

Problem was still happening, my traces showed an "500 Internal server error". I tried manually clearing all the cookies from chumby.com after logging out. Then logging in again. Behavior was the same.

BUT... I tried with *ahem* Internet Explorer  and it worked.

So, after some more investigation, I have discovered that the problem arises when the browser does not send the HTTP Referer header (verified by reloading and deleting/keeping referer header with the Firefox "Tamper Data" plugin)

Could you verify if this is a "byproduct" of the last maintenance? AFAIK I always had my firefox configured not to send HTTP referer and I never had this problem before.


Thanks again

Nixkalo

Re: Some pages unavailable.

nixkalo wrote:

So, after some more investigation, I have discovered that the problem arises when the browser does not send the HTTP Referer header (verified by reloading and deleting/keeping referer header with the Firefox "Tamper Data" plugin)

Could you verify if this is a "byproduct" of the last maintenance? AFAIK I always had my firefox configured not to send HTTP referer and I never had this problem before.

my configuration with respect to HTTP referer blocking hasn't changed for some time.  i've always allowed connections from
browsers that don't send referer info and am only blocking a couple of deep linkers that were abusing our swfs.

if you want to try this again, just tell me from what IP and time range and i'll continue to investigate on our end.

/mdkail

Re: Some pages unavailable.

ok, i found the errors in our logs and will file a bug on this.  in the interim, could you have tamper data not remove the
HTTP_REFERER?

thanks and sorry for the inconvenience.

/mdkail

Re: Some pages unavailable.

Tamper Data was just the tool I used to certify that http referer was the cause, but I don't use it regularly. The usual cause (and solution) that is explained below for those firefox users out there that might experience the same problem:

1) type "about:config" (without the quotes) in the address box
2) type "referer" in the "filter"box that appears
3) verify that "network.http.sendRefererHeader" is set to 2 (the default value).

Regards
   Nixkalo

Re: Some pages unavailable.

Nixkalo,  I am attempting to recreate the problem you are having with FF.  I verified the settings as you noted and then attempted to create a new channel.  I have not been able to duplicate the page not available issue.  Is there any additional information that you can provide to help me set up my environment to reflect your setup.

Thanks
Steve (Chumby QA)

Re: Some pages unavailable.

A bug has been opened to resolve this problem.  The error occurs when the referer is set to 0.

Re: Some pages unavailable.

Steve,

So I assume from your previous mail that you finally were able to reproduce the problem, right? Or do you want me to send you a private message with traces?

By re-reading my mail I guess I expressed it wrongly, Here it is again:

network.http.sendRefererHeader=2 (default value) -> SEND the header -> everything works fine
network.http.sendRefererHeader=0 -> DO NOT send the header -> you get the "no available" error

Sorry about the confusion


Regards
Nixkalo

Re: Some pages unavailable.

No problem Nixkalo, I found that the error occurred when set to 0 and did not occur when set to 2.  You don't need to send anything else, the bug has been filed and hopefully will be resolved soon.

Steve