bad server response
RobertB
whenever I try to access delicious.com. I'm not sure what it does or why
it does it, but it happens with at least two versions of Safari (2.0.4
(419.3) under 10.4.9) and the newer 3.x version included with 10.4.11.
"Safari canąt open the page łhttp://delicious.com/sbarkto˛. The error
was: łbad server response˛ (NSURLErrorDomain:-1011) Please choose Report
Bug to Apple from the Safari menu, note the error number, and describe
what you did before you saw this message."
There's a delicious forum but that hasn't been much help. Several other
complaints about this error appeared, mostly for Safari (but not
exclusively).
Is this a Safari bug, a delicious bug, or something else?
--
"Never believe anything until it's officially denied."
Jolly Roger
RobertB <missi...@cloud9.net> wrote:
Who is your DNS provider?
--
Send responses to the relevant news group rather than to me, as
E-mail sent to this address may be devoured by my very hungry SPAM
filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google
Groups. Use a real news client if you want me to see your posts.
JR
RobertB
Dave Balderstone <dave@N_O_T_T_H_I_Sbalderstone.ca> wrote:
> In article <missinglink-BBD8...@news.cloud9.net>, RobertB
> <missi...@cloud9.net> wrote:
>
> I can access that page using Safari Version 3.1.2 (5525.20.1) under OSX
> 10.5.5
>
> Look to your internet connection, maybe the DNS settings?
DNS settings? What should I look for exactly? The problem occurred after
Delicious revamped their Web site about three weeks ago. While I can't
state conclusively that that's the cause, I'm somewhat suspicious.
RobertB
Jolly Roger <jolly...@pobox.com> wrote:
> In article <missinglink-BBD8...@news.cloud9.net>,
> RobertB <missi...@cloud9.net> wrote:
>
> > For the past two weeks or so, I have been getting the following message
> > whenever I try to access delicious.com. I'm not sure what it does or why
> > it does it, but it happens with at least two versions of Safari (2.0.4
> > (419.3) under 10.4.9) and the newer 3.x version included with 10.4.11.
> >
> >
> > "Safari canąt open the page łhttp://delicious.com/sbarkto˛. The error
> > was: łbad server response˛ (NSURLErrorDomain:-1011) Please choose Report
> > Bug to Apple from the Safari menu, note the error number, and describe
> > what you did before you saw this message."
> >
> > There's a delicious forum but that hasn't been much help. Several other
> > complaints about this error appeared, mostly for Safari (but not
> > exclusively).
> >
> > Is this a Safari bug, a delicious bug, or something else?
>
> Who is your DNS provider?
My ISP.
Gene E. Bloch
> For the past two weeks or so, I have been getting the following message
> whenever I try to access delicious.com. I'm not sure what it does or why
> it does it, but it happens with at least two versions of Safari (2.0.4
> (419.3) under 10.4.9) and the newer 3.x version included with 10.4.11.
> "Safari can¹t open the page ³http://delicious.com/sbarkto². The error
> was: ³bad server response² (NSURLErrorDomain:-1011) Please choose Report
> Bug to Apple from the Safari menu, note the error number, and describe
> what you did before you saw this message."
> There's a delicious forum but that hasn't been much help. Several other
> complaints about this error appeared, mostly for Safari (but not
> exclusively).
> Is this a Safari bug, a delicious bug, or something else?
In addition to Dave Balderstone's response (he *definitely* knows more
than I do), you might consider downloading an additional browser, such
as Firefox or Opera (of course, there are others too) so when that sort
of thing happens you can quickly see whether the problem is in Safari
or elsewhere.
I find that having a few browsers around solves various problems (often
involving the rendering of pages) as they arise :-)
--
Gene E. Bloch (Gino) letters617blochg3251
(replace the numbers by "at" and "dotcom")
RobertB
Dave Balderstone <dave@N_O_T_T_H_I_Sbalderstone.ca> wrote:
> In article <missinglink-9390...@news.cloud9.net>, RobertB
> <missi...@cloud9.net> wrote:
>
> > In article <031020081933456542%dave@N_O_T_T_H_I_Sbalderstone.ca>,
> > Dave Balderstone <dave@N_O_T_T_H_I_Sbalderstone.ca> wrote:
> >
> > > In article <missinglink-BBD8...@news.cloud9.net>, RobertB
> > > <missi...@cloud9.net> wrote:
> > >
> > > > For the past two weeks or so, I have been getting the following message
> > > > whenever I try to access delicious.com. I'm not sure what it does or
> > > > why
> > > > it does it, but it happens with at least two versions of Safari (2.0.4
> > > > (419.3) under 10.4.9) and the newer 3.x version included with 10.4.11.
> > > >
> > > >
> > > > "Safari canąt open the page łhttp://delicious.com/sbarkto˛. The error
> > > > was: łbad server response˛ (NSURLErrorDomain:-1011) Please choose
> > > > Report
> > > > Bug to Apple from the Safari menu, note the error number, and describe
> > > > what you did before you saw this message."
> > > >
> > > > There's a delicious forum but that hasn't been much help. Several other
> > > > complaints about this error appeared, mostly for Safari (but not
> > > > exclusively).
> > > >
> > > > Is this a Safari bug, a delicious bug, or something else?
> > >
> > > I can access that page using Safari Version 3.1.2 (5525.20.1) under OSX
> > > 10.5.5
> > >
> > > Look to your internet connection, maybe the DNS settings?
> >
> > DNS settings? What should I look for exactly?
>
> That the DNS server listed in your Network Preferences pane is
> functioning properly.
>
> > The problem occurred after
> > Delicious revamped their Web site about three weeks ago. While I can't
> > state conclusively that that's the cause, I'm somewhat suspicious.
Hmm. The problem doesn't occure with Firefox 3.0.3, which I just
installed. It's also faster than Safari.
RobertB
Gene E. Bloch <spam...@nobody.invalid> wrote:
> On 10/03/2008, RobertB posted this:
> > For the past two weeks or so, I have been getting the following message
> > whenever I try to access delicious.com. I'm not sure what it does or why
> > it does it, but it happens with at least two versions of Safari (2.0.4
> > (419.3) under 10.4.9) and the newer 3.x version included with 10.4.11.
>
>
> > "Safari can1t open the page 3http://delicious.com/sbarkto2. The error
> > was: 3bad server response2 (NSURLErrorDomain:-1011) Please choose Report
> > Bug to Apple from the Safari menu, note the error number, and describe
> > what you did before you saw this message."
>
> > There's a delicious forum but that hasn't been much help. Several other
> > complaints about this error appeared, mostly for Safari (but not
> > exclusively).
>
> > Is this a Safari bug, a delicious bug, or something else?
>
> In addition to Dave Balderstone's response (he *definitely* knows more
> than I do), you might consider downloading an additional browser, such
> as Firefox or Opera (of course, there are others too) so when that sort
> of thing happens you can quickly see whether the problem is in Safari
> or elsewhere.
>
> I find that having a few browsers around solves various problems (often
> involving the rendering of pages) as they arise :-)
Well, I installed Firefox 3.0.3 and the problem disappears. It's also
faster and does a better job with ad (blocking). So, that would appear
to point to Safari as the problem.
Gene E. Bloch
Good. Glad you found a solution.
Mike Rosenberg
> Well, I installed Firefox 3.0.3 and the problem disappears. It's also
> faster and does a better job with ad (blocking). So, that would appear
> to point to Safari as the problem.
I had no problem viewing your URL here using Safari 3.1.2, so it's not a
general Safari issue. I see, though, that others have had problems with
delicious.com and Safari recently:
http://support.delicious.com/forum/comments.php?DiscussionID=1245&page=1
Are you the person who posted there as sbarkto? If so, it would have
been nice if you had told us from the outset that you'd already learned
that others are having the same problems using Safari there recently.
--
I kill Google Groups posts. See http://improve-usenet.org for details.
<http://designsbymike.net/shop/mac.cgi> Mac and geek T-shirts & gifts
<http://designsbymike.net/shop/prius.cgi> Prius shirts/bumper stickers
<http://designsbymike.net/shop/greet.cgi> Holiday cards with attitude
Jolly Roger
RobertB <missi...@cloud9.net> wrote:
<http://www.port80software.com/200ok/archive/2005/02/25/349.aspx>
RobertB
mike...@TOGROUPmacconsult.com (Mike Rosenberg) wrote:
> RobertB <missi...@cloud9.net> wrote:
>
> > Well, I installed Firefox 3.0.3 and the problem disappears. It's also
> > faster and does a better job with ad (blocking). So, that would appear
> > to point to Safari as the problem.
>
> I had no problem viewing your URL here using Safari 3.1.2, so it's not a
> general Safari issue. I see, though, that others have had problems with
> delicious.com and Safari recently:
>
> http://support.delicious.com/forum/comments.php?DiscussionID=1245&page=1
>
> Are you the person who posted there as sbarkto? If so, it would have
> been nice if you had told us from the outset that you'd already learned
> that others are having the same problems using Safari there recently.
I did. In an earlier post. I said others had reported problems with
other browsers.
RobertB
Jolly Roger <jolly...@pobox.com> wrote:
> In article <missinglink-36EB...@news.cloud9.net>,
> RobertB <missi...@cloud9.net> wrote:
>
> > In article <jollyroger-49BBA...@news.individual.net>,
> > Jolly Roger <jolly...@pobox.com> wrote:
> >
> > > In article <missinglink-BBD8...@news.cloud9.net>,
> > > RobertB <missi...@cloud9.net> wrote:
> > >
> > > > For the past two weeks or so, I have been getting the following message
> > > > whenever I try to access delicious.com. I'm not sure what it does or
> > > > why
> > > > it does it, but it happens with at least two versions of Safari (2.0.4
> > > > (419.3) under 10.4.9) and the newer 3.x version included with 10.4.11.
> > > >
> > > >
> > > > "Safari canąt open the page łhttp://delicious.com/sbarkto˛. The error
> > > > was: łbad server response˛ (NSURLErrorDomain:-1011) Please choose
> > > > Report
> > > > Bug to Apple from the Safari menu, note the error number, and describe
> > > > what you did before you saw this message."
> > > >
> > > > There's a delicious forum but that hasn't been much help. Several other
> > > > complaints about this error appeared, mostly for Safari (but not
> > > > exclusively).
> > > >
> > > > Is this a Safari bug, a delicious bug, or something else?
> > >
> > > Who is your DNS provider?
> >
> > My ISP.
>
> <http://www.port80software.com/200ok/archive/2005/02/25/349.aspx>
I found that same description of the problem on another site. Doesn't
say anything about a DNS server, however. I suppose I should check
Apple's archives to see if this has been discussed.
Jolly Roger
RobertB <missi...@cloud9.net> wrote:
Right. Looks like a Safari bug to me.
Mike Rosenberg
> > I had no problem viewing your URL here using Safari 3.1.2, so it's not a
> > general Safari issue. I see, though, that others have had problems with
> > delicious.com and Safari recently:
> >
> > http://support.delicious.com/forum/comments.php?DiscussionID=1245&page=1
> >
> > Are you the person who posted there as sbarkto? If so, it would have
> > been nice if you had told us from the outset that you'd already learned
> > that others are having the same problems using Safari there recently.
>
> I did. In an earlier post. I said others had reported problems with
> other browsers.
My apologies! It seems clear to me that, since a bunch of people started
having this problem with delicious.com at the same time, there's a
problem at their end. I wonder how Dave and JR both missed this in their
responses.
Mike Rosenberg
> > My apologies! It seems clear to me that, since a bunch of people started
> > having this problem with delicious.com at the same time, there's a
> > problem at their end. I wonder how Dave and JR both missed this in their
> > responses.
>
> I didn't miss it. In fact, it's why I asked about DNS. Multiple
> browsers, but not everyone using a particular browser.
>
> Do try to keep up.
Okay, I admit it, I'm really confused. Since it's a problem a lot of
people are having at that one site, why are we suspecting DNS and not
that site?
RobertB
Dave Balderstone <dave@N_O_T_T_H_I_Sbalderstone.ca> wrote:
> In article <1iocstr.28jk151yf6cnqN%mike...@TOGROUPmacconsult.com>,
> Mike Rosenberg <mike...@TOGROUPmacconsult.com> wrote:
>
> > Dave Balderstone <dave@N_O_T_T_H_I_Sbalderstone.ca> wrote:
> >
> > > > My apologies! It seems clear to me that, since a bunch of people started
> > > > having this problem with delicious.com at the same time, there's a
> > > > problem at their end. I wonder how Dave and JR both missed this in their
> > > > responses.
> > >
> > > I didn't miss it. In fact, it's why I asked about DNS. Multiple
> > > browsers, but not everyone using a particular browser.
> > >
> > > Do try to keep up.
> >
> > Okay, I admit it, I'm really confused. Since it's a problem a lot of
> > people are having at that one site, why are we suspecting DNS and not
> > that site?
>
> Maybe I misread the error message the OP reported, but it certainly
> suggested a DNS error to me.
>
> But the primary reason I didn't suspect the site was because I was able
> to connect to ti without problem, and have been for quite some time.
It *could* still be a DNS problem but the two browsers may respond to
DNS timeouts differently (one possible explanation -- not necessarily
the correct one). So what becomes a problem for Safari isn't for
Firefox.
Mike Rosenberg
> It *could* still be a DNS problem but the two browsers may respond to
> DNS timeouts differently (one possible explanation -- not necessarily
> the correct one). So what becomes a problem for Safari isn't for
> Firefox.
The message you've seen, though, is not the standard message one gets
when there's a timeout.
RobertB
mike...@TOGROUPmacconsult.com (Mike Rosenberg) wrote:
> RobertB <missi...@cloud9.net> wrote:
>
> > It *could* still be a DNS problem but the two browsers may respond to
> > DNS timeouts differently (one possible explanation -- not necessarily
> > the correct one). So what becomes a problem for Safari isn't for
> > Firefox.
>
> The message you've seen, though, is not the standard message one gets
> when there's a timeout.
Don't know. But that was simply an example.