ysearchboss : Messages : 2828-2858 of 5343

sure it would be different from bing

On 11/4/10, Joseph <jrussbowman@...> wrote:
> I can't test results for an api that hasn't been released. :)
>
> The announcement appears to preclude news results coming from Bing, which is
> why I ask.
>
> --- In ysearchboss@yahoogroups.com, kaveh tahernam <kavehtahernam@...>
> wrote:
>>
>> ???!!!!!
>> why do people ask stupid question some time?
>> go and make a test! ;)
>>
>> On 11/1/10, Joseph <jrussbowman@...> wrote:
>> > Going by this sentence "Core web and image results will eventually be
>> > powered by the Microsoft search platform" it appears news results will
>> > not
>> > be powered by Bing in V2?
>> >
>> > What changes, if any, will news see?
>> >
>> > I ask because right now I am pulling news results from Bing for
>> > unscatter.com, but have been considering getting actual search results
>> > from
>> > Boss, as it frees me up to be able to manage advertising on those pages.
>> > Boss news doesn't offer the ability (that I know of) to get generic top
>> > results, so I will probably have to keep Bing powering those landing
>> > pages I
>> > assume?
>> >
>> > I plan on eventually looking back at the original project I started
>> > playing
>> > with boss for at some point, and the main interest there was news as
>> > well.
>> >
>> > Also, will generic YQL queries for search and news cease to work when V2
>> > comes out as everything will have to be oauth enabled? I was
>> > contemplating
>> > pulling some content via javascript in order to save bandwidth by not
>> > having
>> > to act a proxy between the browser and the content when possible for non
>> > core related content.
>> >
>> >
>> >
>> > ------------------------------------
>> >
>> > Yahoo! Groups Links
>> >
>> >
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

#2829

From: "christian.kroll83" <christian.kroll83@...>
Date: Tue Nov 9, 2010 12:09 pm
Subject: ERROR 999: Unable to process request at this time --> DOWN?

christian.kr...

Hi BOSS team,

I am getting these responses from the BOSS API since about 2 hours:

"Sorry, Unable to process request at this time -- error 999."

I get this response from all locations I tried in Germany so far:

http://boss.yahooapis.com/ysearch/web/v1/test?lang=de®ion=de&appid=***&start=\
0&count=10&stats=true

Please help!

#2830

From: Yogish Baliga <yogishb@...>
Date: Tue Nov 9, 2010 1:04 pm
Subject: Re: ERROR 999: Unable to process request at this time --> DOWN?

yogishb

I think you are doing too many requests. You are being blocked by the abuse detection system (error code 999).

http://sg.answers.yahoo.com/question/index?qid=20070614235929AAUbrLP

Yogish Baliga
Monvia Inc./TILE Financial Inc.
VP Of Engineering/Chief Technical Officer(CTO)
Tel: +1 408-480-7988
Email: yogishb@...
baliga@...
baliga@...
Blog:http://dudefrommangalore.blogspot.com/

From: christian.kroll83 <christian.kroll83@...>
To: ysearchboss@yahoogroups.com
Cc:
Sent: Tuesday, November 9, 2010 7:09:41 AM
Subject: [ysearchboss] ERROR 999: Unable to process request at this time --> DOWN?

Hi BOSS team,

I am getting these responses from the BOSS API since about 2 hours:

"Sorry, Unable to process request at this time -- error 999."

I get this response from all locations I tried in Germany so far:

http://boss.yahooapis.com/ysearch/web/v1/test?lang=de&region=de&appid=***&start=0&count=10&stats=true

Please help!

------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ysearchboss/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/ysearchboss/join
(Yahoo! ID required)

<*> To change settings via email:
ysearchboss-digest@yahoogroups.com
ysearchboss-fullfeatured@yahoogroups.com

<*> To unsubscribe from this group, send an email to:
ysearchboss-unsubscribe@yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/

#2831

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Tue Nov 9, 2010 7:31 pm
Subject: Re: ERROR 999: Unable to process request at this time --> DOWN?

sboss64

Christian,

The error you are receiving is indeed an indication that your traffic was caught in our defense filter as being potentially dangerous.� The primary function of the filter is to prevent any abuse from affecting the entire customer base per our terms of service.� We regret any inconvenience this may have caused.

If you can provide you APPID, IP Address used and Website, we will be sure to review it and prevent this type of interruption for you in the future.
You may send those to boss-requests@...

Best Regards,
Yahoo! Support

On 11/9/10 4:09 AM, christian.kroll83 wrote:

�

Hi BOSS team,

I am getting these responses from the BOSS API since about 2 hours:

"Sorry, Unable to process request at this time -- error 999."

I get this response from all locations I tried in Germany so far:

http://boss.yahooapis.com/ysearch/web/v1/test?lang=de&region=de&appid=***&start=0&count=10&stats=true

Please help!

#2832

From: "williammlowe" <w.illlowe@...>
Date: Wed Nov 10, 2010 11:11 pm
Subject: all boss calls result in 403s

williammlowe

Since Nov 1 2010 around 10am Pacific,  every request we've made to BOSS has
returned zero results.  It looks like we're getting 403s:

<!doctype html public "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html><head><title>Yahoo! - 403 Forbidden</title><style>
/* nn4 hide */
/*/*/
body {font:small/1.2em
arial,helvetica,clean,sans-serif;font:x-small;text-align:center;}table
{font-size:inherit;font:x-small;}
html>body {font:83%/1.2em arial,helvetica,clean,sans-serif;}input
{font-size:100%;vertical-align:middle;}p, form {margin:0;padding:0;}
p {padding-bottom:6px;margin-bottom:10px;}#doc {width:48.5em;margin:0
auto;border:1px solid #fff;text-align:center;}#ygma
{text-align:right;margin-bottom:53px}
#ygma img {float:left;}#ygma div {border-bottom:1px solid
#ccc;padding-bottom:8px;margin-left:152px;}#bd
{clear:both;text-align:left;width:75%;margin:0 auto 20px;}
h1 {font-size:135%;text-align:center;margin:0 0 15px;}legend
{display:none;}fieldset {border:0 solid #fff;padding:.8em 0 .8em 4.5em;}
form {position:relative;background:#eee;margin-bottom:15px;border:1px solid
#ccc;border-width:1px 0;}
#s1p {width:15em;margin-right:.1em;}
form span {position:absolute;left:70%;top:.8em;}form a {font:78%/1.2em
arial;display:block;padding-left:.8em;white-space:nowrap;background:
url(http://us.i1.yimg.com/us.yimg.com/i/s/bullet.gif) no-repeat left center;}
form .sep {display:none;}.more {text-align:center;}#ft
{padding-top:10px;border-top:1px solid #999;}#ft p {text-align:center;font:78%
arial;}
/* end nn4 hide */
</style></head>
<body><div id="doc">
<div id="ygma"><a href="http://us.rd.yahoo.com/403/*http://www.yahoo.com"><img
src=http://us.i1.yimg.com/us.yimg.com/i/yahoo.gif
width=147 height=31 border=0 alt="Yahoo!"></a><div><a
href="http://us.rd.yahoo.com/403/*http://www.yahoo.com">Yahoo!</a>
- <a
href="http://us.rd.yahoo.com/403/*http://help.yahoo.com">Help</a></div></div>
<div id="bd"><h1>Sorry, Forbidden.</h1>
You don't have permission to access this URL on this server.<P>
<P>Additionally, a 403 Forbidden
error was encountered while trying to use an ErrorDocument to handle the
request.
<p>Please check the URL for proper spelling and capitalization. If
you're having trouble locating a destination on Yahoo!, try visiting the
<strong><a
href="http://us.rd.yahoo.com/403/*http://www.yahoo.com">Yahoo! home
page</a></strong> or look through a list of <strong><a
href="http://us.rd.yahoo.com/403/*http://docs.yahoo.com/docs/family/more/">Yahoo\
!'s
online services</a></strong>. Also, you may find what you're looking for
if you try searching below.</p>
<form name="s1"
action="http://us.rd.yahoo.com/403/*-http://search.yahoo.com/search"><fieldset>
<legend><label for="s1p">Search the Web</label></legend>
<input type="text" size=30 name="p" id="s1p" title="enter search terms here">
<input type="submit" value="Search">
<span><a
href="http://us.rd.yahoo.com/403/*http://search.yahoo.com/search/options?p=">adv\
anced search</a> <span class=sep>|</span> <a
href="http://us.rd.yahoo.com/403/*http://buzz.yahoo.com">most popular</a></span>
</fieldset></form>
<p class="more">Please try <strong><a
href="http://us.rd.yahoo.com/403/*http://help.yahoo.com">Yahoo!
Help Central</a></strong> if you need more assistance.</p>
</div><div id="ft"><p>Copyright © 2010 Yahoo! Inc.
All rights reserved. <a
href="http://us.rd.yahoo.com/403/*http://privacy.yahoo.com">Privacy
Policy</a> - <a
href="http://us.rd.yahoo.com/403/*http://docs.yahoo.com/info/terms/">Terms
of Service</a></p></div>
</div></body></html>

... is this intentional?  Are we doing something wrong?

Thanks!

#2833

From: "matthias.maschek" <matthias.maschek@...>
Date: Mon Nov 15, 2010 9:15 am
Subject: Cover search through Image Search

matthias.mas...

Hi!

I have a question regarding the Image Search.

I want to use it to automatically find Covers for a MP3 Player.
Am i still inside of the BOSS license since i'm not showing where i found the
image (Would be strange in the player)?

What is the official statement from Yahoo?

Thanks,
Matthias

#2834

From: "derekthejew@..." <derekthejew@...>
Date: Mon Nov 15, 2010 7:23 pm
Subject: BOSS search timing out

derekthejew...

Up until a few weeks ago we had been using the BOSS search service quite
effectively on www.trendhunter.com

Recently all search results end in timeout. The appid wasn't returning results
in a simple browser query so we got a new one that did. However running through
our web servers still results in timeouts. Has our site been flagged for some
reason?

Please let me know,
-Derek

#2835

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Mon Nov 15, 2010 11:19 pm
Subject: Re: BOSS search timing out

sboss64

Hello Derek,

When a BOSS user is blocked, they would receive a "999" HTTP error code back, for their BOSS API calls.� You should now check your web server log files, for the time period in question.� If you do find this to be the situation, please send an email to boss-requests@....� This email should include your APP ID(s), IP address(es), and then just repeat your site URL of http://www.trendhunter.com/.�� Somebody will investigate the block circumstances, and get back to you.

But if you can confirm that you do not have any "999" HTTP error codes in your web server log files for that time period, then this instead does sound like a true timeout situation.� (network issue, etc.)�� From the exact time period of having a failure, please post the following details here in the user group� (to allow anybody to assist you, including the general BOSS user community):�� http://tech.groups.yahoo.com/group/ysearchboss/message/2574

Thank you,
Jay

On 11/15/10 11:23 AM, derekthejew@... wrote:

�

Up until a few weeks ago we had been using the BOSS search service quite effectively on www.trendhunter.com

Recently all search results end in timeout. The appid wasn't returning results in a simple browser query so we got a new one that did. However running through our web servers still results in timeouts. Has our site been flagged for some reason?

Please let me know,
-Derek

#2836

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Mon Nov 15, 2010 11:30 pm
Subject: Re: BOSS search timing out

sboss64

Slight correction:

Not your web server log files, but rather where you log details about what HTTP response you get back from all of your BOSS API calls.�� I'm not sure how you wrote and implemented your site.

Or if your code currently does not log basic details on each BOSS request + response back, then it would be a good idea to implement some type of basic BOSS-related logging within your code, for future troubleshooting benefit.

The other developers here in this user group should be able to provide some ideas, of different ways to code this.

Thanks,
Jay

On 11/15/10 3:19 PM, BOSS User Group Support Team wrote:

�

Hello Derek,

When a BOSS user is blocked, they would receive a "999" HTTP error code back, for their BOSS API calls.� You should now check your web server log files, for the time period in question.� If you do find this to be the situation, please send an email to boss-requests@....� This email should include your APP ID(s), IP address(es), and then just repeat your site URL of http://www.trendhunter.com/.�� Somebody will investigate the block circumstances, and get back to you.

But if you can confirm that you do not have any "999" HTTP error codes in your web server log files for that time period, then this instead does sound like a true timeout situation.� (network issue, etc.)�� From the exact time period of having a failure, please post the following details here in the user group� (to allow anybody to assist you, including the general BOSS user community):�� http://tech.groups.yahoo.com/group/ysearchboss/message/2574

Thank you,
Jay

On 11/15/10 11:23 AM, derekthejew@... wrote:

�

Up until a few weeks ago we had been using the BOSS search service quite effectively on www.trendhunter.com

Recently all search results end in timeout. The appid wasn't returning results in a simple browser query so we got a new one that did. However running through our web servers still results in timeouts. Has our site been flagged for some reason?

Please let me know,
-Derek

#2837

From: "harshadajog" <harshadajog@...>
Date: Tue Nov 16, 2010 6:37 am
Subject: Re-ordering results and removing unwanted results

harshadajog

Is there any way to filter out the unwanted results? For example, the search
results include Comments put in by the user and I do not need those. I also
would like to re-order the results as per their relevance.
Any documentation links/articles would be very much appreciated.

#2838

From: Ted Drake <tdrake@...>
Date: Tue Nov 16, 2010 3:59 pm
Subject: RE: Re-ordering results and removing unwanted results

t_drake_net

http://developer.yahoo.com/blogs/ydn/posts/2009/06/trainspotting_boss/

BOSS allows you to reorder, remove, and insert elements into the result set. That is what makes BOSS special.

You can use url query params to avoid certain sections, for instance –inurl:comments would avoid returning pages that have /comments in the url. You could also do –intitle:comments which would remove pages that have comments in the title. These affect the results returned from BOSS.

You could also create your own logic that parsed the result set and removes results that match your concerns.

I do some simple reranking on my sites. I build an array of the most popular keyterms from all of the results. I then move any result’s whose #1 keyterm matches the pages overall #1 keyterm. You can come up with whatever pattern works for you.

Here are some posts that I have written about modifying BOSS results

http://www.slideshare.net/7mary4/yahoo-boss-and-trainspotting

http://developer.yahoo.com/blogs/ydn/posts/2009/04/boss_updates/

Ted

From: ysearchboss@yahoogroups.com [mailto:ysearchboss@yahoogroups.com] On Behalf Of harshadajog
Sent: Monday, November 15, 2010 10:38 PM
To: ysearchboss@yahoogroups.com
Subject: [ysearchboss] Re-ordering results and removing unwanted results

Is there any way to filter out the unwanted results? For example, the search results include Comments put in by the user and I do not need those. I also would like to re-order the results as per their relevance.
Any documentation links/articles would be very much appreciated.

#2839

From: "derekthejew@..." <derekthejew@...>
Date: Tue Nov 16, 2010 9:31 pm
Subject: Yahoo Boss Timeout

derekthejew...

I have gathered the requested information for help. To reiterate the issue: up
until recently we had been using Yahoo BOSS effectively on TrendHunter.com for a
variety of services. Recently any calls to Yahoo Boss from our web servers have
resulted in a timeout. Calls made locally using our browsers return results as
expected. A wget from our servers produces a timeout. Please let me know what
can be done to resolve this situation.

The exact error is:

Connecting to boss.yahooapis.com|98.136.114.186|:80... failed: Connection timed
out.
Retrying.


A query that times out:

"http://boss.yahooapis.com/ysearch/web/v1/cars?appid={APPID}&format=xml"

Time gathered:

  Nov 16 11:57 EST


Traceroute:

  1  lw-dc2-dist3-vlan181.rtr.liquidweb.com (67.225.198.2)  1.119 ms  0.913 ms  1
.261 ms
  2  lw-dc2-core4-po3.rtr.liquidweb.com (209.59.157.233)  0.560 ms  0.510 ms *
  3  209.59.157.107 (209.59.157.107)  1.466 ms  1.205 ms  1.178 ms
  4  lw-border2-te12.rtr.liquidweb.com (209.59.157.207)  8.077 ms  8.015 ms *
  5  xe-5-0-0.edge2.Chicago2.Level3.net (4.59.29.77)  7.517 ms  7.483 ms  7.474 m
s
  6  vlan52.ebr2.Chicago2.Level3.net (4.69.138.190)  7.584 ms  7.587 ms  7.589 ms
  7  * ae-6-6.ebr2.Washington12.Level3.net (4.69.148.145)  20.798 ms  20.739 ms
  8  ae-5-5.ebr2.Washington1.Level3.net (4.69.143.221)  22.861 ms  22.982 ms  23.
040 ms
  9  ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  21.598 ms ae-62-62.csw1
.Washington1.Level3.net (4.69.134.146)  23.147 ms  35.325 ms
10  ae-41-99.car1.Washington1.Level3.net (4.68.17.195)  22.076 ms ae-21-79.car1.
Washington1.Level3.net (4.68.17.67)  23.710 ms *
11  YAHOO-INC.car1.Washington1.Level3.net (4.79.228.2)  31.853 ms  31.080 ms  31
.260 ms
12  xe-7-0-0.msr1.ac2.yahoo.com (216.115.108.125)  31.411 ms  92.358 ms xe-7-0-0
.msr2.ac2.yahoo.com (216.115.108.129)  31.367 ms
13  xe-2-2-0.clr4.ac4.yahoo.com (72.30.96.5)  49.771 ms xe-5-2-0.clr4.ac4.yahoo.
com (76.13.1.113)  31.410 ms xe-3-2-0.clr4.ac4.yahoo.com (72.30.96.7)  31.155 ms
14  UNKNOWN-76-13-0-23.yahoo.com (76.13.0.23)  31.600 ms  31.639 ms te-8-1.bas-a
1.ac4.yahoo.com (76.13.0.173)  31.324 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Thanks,
-Derek

#2840

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Wed Nov 17, 2010 6:55 pm
Subject: Re: Yahoo Boss Timeout

sboss64

Hello Derek,

Thank you for providing the below helpful troubleshooting information.� Appreciate that.

I will get back to you later today, regarding my analysis.

Thank you,
Jay

On 11/16/10 1:31 PM, derekthejew@... wrote:

�

I have gathered the requested information for help. To reiterate the issue: up until recently we had been using Yahoo BOSS effectively on TrendHunter.com for a variety of services. Recently any calls to Yahoo Boss from our web servers have resulted in a timeout. Calls made locally using our browsers return results as expected. A wget from our servers produces a timeout. Please let me know what can be done to resolve this situation.

The exact error is:

Connecting to boss.yahooapis.com|98.136.114.186|:80... failed: Connection timed out.
Retrying.

A query that times out:

"http://boss.yahooapis.com/ysearch/web/v1/cars?appid={APPID}&format=xml"

Time gathered:

Nov 16 11:57 EST

Traceroute:

1 lw-dc2-dist3-vlan181.rtr.liquidweb.com (67.225.198.2) 1.119 ms 0.913 ms 1 .261 ms
2 lw-dc2-core4-po3.rtr.liquidweb.com (209.59.157.233) 0.560 ms 0.510 ms *
3 209.59.157.107 (209.59.157.107) 1.466 ms 1.205 ms 1.178 ms
4 lw-border2-te12.rtr.liquidweb.com (209.59.157.207) 8.077 ms 8.015 ms *
5 xe-5-0-0.edge2.Chicago2.Level3.net (4.59.29.77) 7.517 ms 7.483 ms 7.474 m s
6 vlan52.ebr2.Chicago2.Level3.net (4.69.138.190) 7.584 ms 7.587 ms 7.589 ms
7 * ae-6-6.ebr2.Washington12.Level3.net (4.69.148.145) 20.798 ms 20.739 ms
8 ae-5-5.ebr2.Washington1.Level3.net (4.69.143.221) 22.861 ms 22.982 ms 23. 040 ms
9 ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 21.598 ms ae-62-62.csw1 .Washington1.Level3.net (4.69.134.146) 23.147 ms 35.325 ms
10 ae-41-99.car1.Washington1.Level3.net (4.68.17.195) 22.076 ms ae-21-79.car1. Washington1.Level3.net (4.68.17.67) 23.710 ms *
11 YAHOO-INC.car1.Washington1.Level3.net (4.79.228.2) 31.853 ms 31.080 ms 31 .260 ms
12 xe-7-0-0.msr1.ac2.yahoo.com (216.115.108.125) 31.411 ms 92.358 ms xe-7-0-0 .msr2.ac2.yahoo.com (216.115.108.129) 31.367 ms
13 xe-2-2-0.clr4.ac4.yahoo.com (72.30.96.5) 49.771 ms xe-5-2-0.clr4.ac4.yahoo. com (76.13.1.113) 31.410 ms xe-3-2-0.clr4.ac4.yahoo.com (72.30.96.7) 31.155 ms
14 UNKNOWN-76-13-0-23.yahoo.com (76.13.0.23) 31.600 ms 31.639 ms te-8-1.bas-a 1.ac4.yahoo.com (76.13.0.173) 31.324 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Thanks,
-Derek

#2841

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Thu Nov 18, 2010 1:09 am
Subject: Re: Yahoo Boss Timeout

sboss64

Hello Derek,

I've checked the following, so far:

�� * We were not already having a general outage, at the below time/date.
�� * I don't see your site's IP address in our error log files, to help explain the issue.

So I will now email you separately from this public user group, and work with you individually.

That way we can discuss your current APP ID being used and other details, more appropriately.

-------

Thanks,
Jay

On 11/16/10 1:31 PM, derekthejew@... wrote:

�

I have gathered the requested information for help. To reiterate the issue: up until recently we had been using Yahoo BOSS effectively on TrendHunter.com for a variety of services. Recently any calls to Yahoo Boss from our web servers have resulted in a timeout. Calls made locally using our browsers return results as expected. A wget from our servers produces a timeout. Please let me know what can be done to resolve this situation.

The exact error is:

Connecting to boss.yahooapis.com|98.136.114.186|:80... failed: Connection timed out.
Retrying.

A query that times out:

"http://boss.yahooapis.com/ysearch/web/v1/cars?appid={APPID}&format=xml"

Time gathered:

Nov 16 11:57 EST

Traceroute:

1 lw-dc2-dist3-vlan181.rtr.liquidweb.com (67.225.198.2) 1.119 ms 0.913 ms 1 .261 ms
2 lw-dc2-core4-po3.rtr.liquidweb.com (209.59.157.233) 0.560 ms 0.510 ms *
3 209.59.157.107 (209.59.157.107) 1.466 ms 1.205 ms 1.178 ms
4 lw-border2-te12.rtr.liquidweb.com (209.59.157.207) 8.077 ms 8.015 ms *
5 xe-5-0-0.edge2.Chicago2.Level3.net (4.59.29.77) 7.517 ms 7.483 ms 7.474 m s
6 vlan52.ebr2.Chicago2.Level3.net (4.69.138.190) 7.584 ms 7.587 ms 7.589 ms
7 * ae-6-6.ebr2.Washington12.Level3.net (4.69.148.145) 20.798 ms 20.739 ms
8 ae-5-5.ebr2.Washington1.Level3.net (4.69.143.221) 22.861 ms 22.982 ms 23. 040 ms
9 ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 21.598 ms ae-62-62.csw1 .Washington1.Level3.net (4.69.134.146) 23.147 ms 35.325 ms
10 ae-41-99.car1.Washington1.Level3.net (4.68.17.195) 22.076 ms ae-21-79.car1. Washington1.Level3.net (4.68.17.67) 23.710 ms *
11 YAHOO-INC.car1.Washington1.Level3.net (4.79.228.2) 31.853 ms 31.080 ms 31 .260 ms
12 xe-7-0-0.msr1.ac2.yahoo.com (216.115.108.125) 31.411 ms 92.358 ms xe-7-0-0 .msr2.ac2.yahoo.com (216.115.108.129) 31.367 ms
13 xe-2-2-0.clr4.ac4.yahoo.com (72.30.96.5) 49.771 ms xe-5-2-0.clr4.ac4.yahoo. com (76.13.1.113) 31.410 ms xe-3-2-0.clr4.ac4.yahoo.com (72.30.96.7) 31.155 ms
14 UNKNOWN-76-13-0-23.yahoo.com (76.13.0.23) 31.600 ms 31.639 ms te-8-1.bas-a 1.ac4.yahoo.com (76.13.0.173) 31.324 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

Thanks,
-Derek

#2842

From: "williammlowe" <w.illlowe@...>
Date: Thu Nov 18, 2010 4:52 am
Subject: Re: all boss calls result in 403s

williammlowe

I haven't seen any reply to this from the BOSS team.  Any of you guys know what
might be going on here?  What information can we provide to help debug it?

Thanks,

Will

--- In ysearchboss@yahoogroups.com, "williammlowe" <w.illlowe@...> wrote:
>
> Since Nov 1 2010 around 10am Pacific,  every request we've made to BOSS has
returned zero results.  It looks like we're getting 403s:
>
> <!doctype html public "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
> <html><head><title>Yahoo! - 403 Forbidden</title><style>
> /* nn4 hide */
> /*/*/
> body {font:small/1.2em
arial,helvetica,clean,sans-serif;font:x-small;text-align:center;}table
{font-size:inherit;font:x-small;}
> html>body {font:83%/1.2em arial,helvetica,clean,sans-serif;}input
{font-size:100%;vertical-align:middle;}p, form {margin:0;padding:0;}
> p {padding-bottom:6px;margin-bottom:10px;}#doc {width:48.5em;margin:0
auto;border:1px solid #fff;text-align:center;}#ygma
{text-align:right;margin-bottom:53px}
> #ygma img {float:left;}#ygma div {border-bottom:1px solid
#ccc;padding-bottom:8px;margin-left:152px;}#bd
{clear:both;text-align:left;width:75%;margin:0 auto 20px;}
> h1 {font-size:135%;text-align:center;margin:0 0 15px;}legend
{display:none;}fieldset {border:0 solid #fff;padding:.8em 0 .8em 4.5em;}
> form {position:relative;background:#eee;margin-bottom:15px;border:1px solid
#ccc;border-width:1px 0;}
> #s1p {width:15em;margin-right:.1em;}
> form span {position:absolute;left:70%;top:.8em;}form a {font:78%/1.2em
arial;display:block;padding-left:.8em;white-space:nowrap;background:
url(http://us.i1.yimg.com/us.yimg.com/i/s/bullet.gif) no-repeat left center;}
> form .sep {display:none;}.more {text-align:center;}#ft
{padding-top:10px;border-top:1px solid #999;}#ft p {text-align:center;font:78%
arial;}
> /* end nn4 hide */
> </style></head>
> <body><div id="doc">
> <div id="ygma"><a href="http://us.rd.yahoo.com/403/*http://www.yahoo.com"><img
> src=http://us.i1.yimg.com/us.yimg.com/i/yahoo.gif
> width=147 height=31 border=0 alt="Yahoo!"></a><div><a
> href="http://us.rd.yahoo.com/403/*http://www.yahoo.com">Yahoo!</a>
> - <a
href="http://us.rd.yahoo.com/403/*http://help.yahoo.com">Help</a></div></div>
> <div id="bd"><h1>Sorry, Forbidden.</h1>
> You don't have permission to access this URL on this server.<P>
> <P>Additionally, a 403 Forbidden
> error was encountered while trying to use an ErrorDocument to handle the
request.
> <p>Please check the URL for proper spelling and capitalization. If
> you're having trouble locating a destination on Yahoo!, try visiting the
> <strong><a
> href="http://us.rd.yahoo.com/403/*http://www.yahoo.com">Yahoo! home
> page</a></strong> or look through a list of <strong><a
>
href="http://us.rd.yahoo.com/403/*http://docs.yahoo.com/docs/family/more/">Yahoo\
!'s
> online services</a></strong>. Also, you may find what you're looking for
> if you try searching below.</p>
> <form name="s1"
action="http://us.rd.yahoo.com/403/*-http://search.yahoo.com/search"><fieldset>
> <legend><label for="s1p">Search the Web</label></legend>
> <input type="text" size=30 name="p" id="s1p" title="enter search terms here">
> <input type="submit" value="Search">
> <span><a
href="http://us.rd.yahoo.com/403/*http://search.yahoo.com/search/options?p=">adv\
anced search</a> <span class=sep>|</span> <a
href="http://us.rd.yahoo.com/403/*http://buzz.yahoo.com">most popular</a></span>
> </fieldset></form>
> <p class="more">Please try <strong><a
> href="http://us.rd.yahoo.com/403/*http://help.yahoo.com">Yahoo!
> Help Central</a></strong> if you need more assistance.</p>
> </div><div id="ft"><p>Copyright © 2010 Yahoo! Inc.
> All rights reserved. <a
> href="http://us.rd.yahoo.com/403/*http://privacy.yahoo.com">Privacy
> Policy</a> - <a
> href="http://us.rd.yahoo.com/403/*http://docs.yahoo.com/info/terms/">Terms
> of Service</a></p></div>
> </div></body></html>
>
> ... is this intentional?  Are we doing something wrong?
>
> Thanks!
>

#2843

From: B Singor <bsingor@...>
Date: Thu Nov 18, 2010 10:39 am
Subject: Yahoo Boss Timeout

bsingor

Our website makes use of the Yahoo! BOSS search API. Unfortunately your service stopped responding to our search requests, a few months ago. Any calls to Yahoo Boss from our web servers have resulted in a timeout.

I hope you can help me.

http://boss.yahooapis.com/ysearch/web/v1/test?appid={APPID}&format=json

Resolving boss-api.a1.b.yahoo.com... 98.136.114.186
Connecting to boss-api.a1.b.yahoo.com|98.136.114.186|:80... failed: Connection timed out.
Retrying.

1 rt-gs01-v54.xl-is.net (79.170.91.2) 0.596 ms 0.578 ms 0.557 ms
2 rt-eu01-v2.xl-is.net (79.170.92.19) 4.801 ms 4.810 ms 5.040 ms
3 xl-internetservices.nikhef.openpeering.nl (217.170.0.225) 1.144 ms 1.094 ms 8.354 ms
4 ge-1-3-0.pat1.ams.yahoo.com (195.69.145.110) 1.660 ms 1.651 ms 1.631 ms
5 ge-0-2-0.pat2.ams.yahoo.com (66.196.65.71) 1.628 ms 1.590 ms 1.572 ms
6 so-2-0-0.pat1.the.yahoo.com (66.196.65.67) 7.154 ms 7.583 ms 7.467 ms
7 as-0.pat1.nyc.yahoo.com (66.196.65.13) 84.191 ms 84.121 ms UNKNOWN-216-115-96-30.yahoo.com (216.115.96.30) 85.726 ms
8 ae-8.pat1.dcp.yahoo.com (216.115.101.157) 89.106 ms 89.025 ms UNKNOWN-216-115-100-92.yahoo.com (216.115.100.92) 91.643 ms
9 xe-4-0-0.msr2.ac2.yahoo.com (216.115.108.143) 90.944 ms xe-8-0-0.msr2.ac2.yahoo.com (216.115.108.137) 91.329 ms xe-9-0-0.msr2.ac2.yahoo.com (216.115.108.145) 90.307 ms
10 xe-2-2-0.clr3.ac4.yahoo.com (72.30.96.1) 89.822 ms xe-5-2-0.clr4.ac4.yahoo.com (76.13.1.113) 112.581 ms xe-9-2-0.clr4.ac4.yahoo.com (72.30.96.13) 90.996 ms
11 ge-0-0-0.clr2.ac4.yahoo.com (76.13.0.29) 91.606 ms te-9-1.bas-a2.ac4.yahoo.com (76.13.0.179) 91.597 ms 90.830 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *

Thanks,

Bob

#2844

From: "mfcsfs" <sfs@...>
Date: Thu Nov 18, 2010 12:56 pm
Subject: Re: all boss calls result in 403s

mfcsfs

Hello Will,

I had seen a similar problem. Change your APIKey and the show is going on... I
think Yahoo has changed its authentification.

Regards

Simon

--- In ysearchboss@yahoogroups.com, "williammlowe" <w.illlowe@...> wrote:
>
> I haven't seen any reply to this from the BOSS team.  Any of you guys know
what might be going on here?  What information can we provide to help debug it?
>
> Thanks,
>
> Will
>
> --- In ysearchboss@yahoogroups.com, "williammlowe" <w.illlowe@> wrote:
> >
> > Since Nov 1 2010 around 10am Pacific,  every request we've made to BOSS has
returned zero results.  It looks like we're getting 403s:
> >
> > <!doctype html public "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
> > <html><head><title>Yahoo! - 403 Forbidden</title><style>
> > /* nn4 hide */
> > /*/*/
> > body {font:small/1.2em
arial,helvetica,clean,sans-serif;font:x-small;text-align:center;}table
{font-size:inherit;font:x-small;}
> > html>body {font:83%/1.2em arial,helvetica,clean,sans-serif;}input
{font-size:100%;vertical-align:middle;}p, form {margin:0;padding:0;}
> > p {padding-bottom:6px;margin-bottom:10px;}#doc {width:48.5em;margin:0
auto;border:1px solid #fff;text-align:center;}#ygma
{text-align:right;margin-bottom:53px}
> > #ygma img {float:left;}#ygma div {border-bottom:1px solid
#ccc;padding-bottom:8px;margin-left:152px;}#bd
{clear:both;text-align:left;width:75%;margin:0 auto 20px;}
> > h1 {font-size:135%;text-align:center;margin:0 0 15px;}legend
{display:none;}fieldset {border:0 solid #fff;padding:.8em 0 .8em 4.5em;}
> > form {position:relative;background:#eee;margin-bottom:15px;border:1px solid
#ccc;border-width:1px 0;}
> > #s1p {width:15em;margin-right:.1em;}
> > form span {position:absolute;left:70%;top:.8em;}form a {font:78%/1.2em
arial;display:block;padding-left:.8em;white-space:nowrap;background:
url(http://us.i1.yimg.com/us.yimg.com/i/s/bullet.gif) no-repeat left center;}
> > form .sep {display:none;}.more {text-align:center;}#ft
{padding-top:10px;border-top:1px solid #999;}#ft p {text-align:center;font:78%
arial;}
> > /* end nn4 hide */
> > </style></head>
> > <body><div id="doc">
> > <div id="ygma"><a
href="http://us.rd.yahoo.com/403/*http://www.yahoo.com"><img
> > src=http://us.i1.yimg.com/us.yimg.com/i/yahoo.gif
> > width=147 height=31 border=0 alt="Yahoo!"></a><div><a
> > href="http://us.rd.yahoo.com/403/*http://www.yahoo.com">Yahoo!</a>
> > - <a
href="http://us.rd.yahoo.com/403/*http://help.yahoo.com">Help</a></div></div>
> > <div id="bd"><h1>Sorry, Forbidden.</h1>
> > You don't have permission to access this URL on this server.<P>
> > <P>Additionally, a 403 Forbidden
> > error was encountered while trying to use an ErrorDocument to handle the
request.
> > <p>Please check the URL for proper spelling and capitalization. If
> > you're having trouble locating a destination on Yahoo!, try visiting the
> > <strong><a
> > href="http://us.rd.yahoo.com/403/*http://www.yahoo.com">Yahoo! home
> > page</a></strong> or look through a list of <strong><a
> >
href="http://us.rd.yahoo.com/403/*http://docs.yahoo.com/docs/family/more/">Yahoo\
!'s
> > online services</a></strong>. Also, you may find what you're looking for
> > if you try searching below.</p>
> > <form name="s1"
action="http://us.rd.yahoo.com/403/*-http://search.yahoo.com/search"><fieldset>
> > <legend><label for="s1p">Search the Web</label></legend>
> > <input type="text" size=30 name="p" id="s1p" title="enter search terms
here">
> > <input type="submit" value="Search">
> > <span><a
href="http://us.rd.yahoo.com/403/*http://search.yahoo.com/search/options?p=">adv\
anced search</a> <span class=sep>|</span> <a
href="http://us.rd.yahoo.com/403/*http://buzz.yahoo.com">most popular</a></span>
> > </fieldset></form>
> > <p class="more">Please try <strong><a
> > href="http://us.rd.yahoo.com/403/*http://help.yahoo.com">Yahoo!
> > Help Central</a></strong> if you need more assistance.</p>
> > </div><div id="ft"><p>Copyright © 2010 Yahoo! Inc.
> > All rights reserved. <a
> > href="http://us.rd.yahoo.com/403/*http://privacy.yahoo.com">Privacy
> > Policy</a> - <a
> > href="http://us.rd.yahoo.com/403/*http://docs.yahoo.com/info/terms/">Terms
> > of Service</a></p></div>
> > </div></body></html>
> >
> > ... is this intentional?  Are we doing something wrong?
> >
> > Thanks!
> >
>

#2845

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Fri Nov 19, 2010 1:08 am
Subject: Regarding BOSS timeout issues (for all users)

sboss64

Hello BOSS users,

We are currently performing upgrades to our hardware which may be causing
intermittent timeout issues for a small % of BOSS users.

These timeout issues should be resolved when the upgrades are complete. We will
update the forums at that time.

Thank you,
Jay

#2846

From: BOSS User Group Support Team <boss-usergroup-support-team@...>
Date: Fri Nov 19, 2010 11:19 pm
Subject: upgrades complete --- Re: Regarding BOSS timeout issues (for all users)

sboss64

Hello again,

The upgrades to the BOSS production environment are now complete.

So if you are still experiencing timeout issues, please post here to the BOSS user group again.�� Somebody from our Support team will investigate.

Thank you,
Jay

On 11/18/10 5:08 PM, BOSS User Group Support Team wrote:

�

Hello BOSS users,

We are currently performing upgrades to our hardware which may be causing intermittent timeout issues for a small % of BOSS users.

These timeout issues should be resolved when the upgrades are complete. We will update the forums at that time.

Thank you,
Jay

#2848

From: "sandi.schleicher" <sandi.schleicher@...>
Date: Wed Nov 24, 2010 2:21 pm
Subject: Our servers are getting a 999 error from Yahoo Boss

sandi.schlei...

We've been using the Yahoo BOSS API for over a year with no problem.  Today,
suddenly we start hitting this error.  Can anyone help me figure out what is
going wrong?  See error below:




Sorry, Unable to process request at this time -- error 999.
   Unfortunately we are unable to process your request at this time. This error
is usually temporary. Please try again later.

If you continue to experience this error, it may be caused by one of the
following:

You may want to scan your system for spyware and viruses, as they may interfere
with your ability to connect to Yahoo!. For detailed information on spyware and
virus protection, please visit the Yahoo! Security Center.
This problem may be due to unusual network activity coming from your Internet
Service Provider. We recommend that you report this problem to them.
While this error is usually temporary, if it continues and the above solutions
don't resolve your problem, please let us know.

Return to Yahoo!


Please try Yahoo! Help Central if you need more assistance.

Reply | Messages in this Topic (6)

#2849

From: "sandi.schleicher" <sandi.schleicher@...>
Date: Wed Nov 24, 2010 5:42 pm
Subject: Re: Our servers are getting a 999 error from Yahoo Boss

sandi.schlei...

Looks like a BOSS API issue.  Feed is working properly now with no change from
our side other than turning it off for a few hours.

Anyone else experience this today?

Sandi


--- In ysearchboss@yahoogroups.com, "sandi.schleicher" <sandi.schleicher@...>
wrote:
>
> We've been using the Yahoo BOSS API for over a year with no problem.  Today,
suddenly we start hitting this error.  Can anyone help me figure out what is
going wrong?  See error below:
>
>
>
>
> Sorry, Unable to process request at this time -- error 999.
>   Unfortunately we are unable to process your request at this time. This error
is usually temporary. Please try again later.
>
> If you continue to experience this error, it may be caused by one of the
following:
>
> You may want to scan your system for spyware and viruses, as they may
interfere with your ability to connect to Yahoo!. For detailed information on
spyware and virus protection, please visit the Yahoo! Security Center.
> This problem may be due to unusual network activity coming from your Internet
Service Provider. We recommend that you report this problem to them.
> While this error is usually temporary, if it continues and the above solutions
don't resolve your problem, please let us know.
>
> Return to Yahoo!
>
>
> Please try Yahoo! Help Central if you need more assistance.
>

Reply | Messages in this Topic (6)

#2850

From: "sandi.schleicher" <sandi.schleicher@...>
Date: Wed Nov 24, 2010 5:49 pm
Subject: Re: Our servers are getting a 999 error from Yahoo Boss

sandi.schlei...

Yahoo BOSS team,

Our web sites that these requests are coming from our www.igive.com and
isearch.igive.com.

The IP address is 208.100.26.90 but we also have some servers in the Amazon
cloud (184.73.163.90).

Can you white list these for us?

Sandi



--- In ysearchboss@yahoogroups.com, "sandi.schleicher" <sandi.schleicher@...>
wrote:
>
> Looks like a BOSS API issue.  Feed is working properly now with no change from
our side other than turning it off for a few hours.
>
> Anyone else experience this today?
>
> Sandi
>
>
> --- In ysearchboss@yahoogroups.com, "sandi.schleicher" <sandi.schleicher@>
wrote:
> >
> > We've been using the Yahoo BOSS API for over a year with no problem.  Today,
suddenly we start hitting this error.  Can anyone help me figure out what is
going wrong?  See error below:
> >
> >
> >
> >
> > Sorry, Unable to process request at this time -- error 999.
> >   Unfortunately we are unable to process your request at this time. This
error is usually temporary. Please try again later.
> >
> > If you continue to experience this error, it may be caused by one of the
following:
> >
> > You may want to scan your system for spyware and viruses, as they may
interfere with your ability to connect to Yahoo!. For detailed information on
spyware and virus protection, please visit the Yahoo! Security Center.
> > This problem may be due to unusual network activity coming from your
Internet Service Provider. We recommend that you report this problem to them.
> > While this error is usually temporary, if it continues and the above
solutions don't resolve your problem, please let us know.
> >
> > Return to Yahoo!
> >
> >
> > Please try Yahoo! Help Central if you need more assistance.
> >
>

Reply | Messages in this Topic (6)

#2851

From: Luis Siquot <lsiq@...>
Date: Thu Nov 25, 2010 2:21 pm
Subject: code example to retrive Incoming Links

lsiq

Please can you point me a code example to retrive incoming links using Yhaoo boss

I was using the site explorer api:
http://search.yahooapis.com/SiteExplorerService/V1/inlinkData

but I want to give a try to the Yahoo boss.

Excuse my poor english

Thanks in advance

�� Luis Siquot

#2852

From: "jtothecro" <jasoncrowder@...>
Date: Mon Dec 13, 2010 2:35 am
Subject: Specifying the kind of image file to search for

jtothecro

With the deprecated Yahoo! Image Search api, when searching for images you could
specify the type of image you would like to search for (png, bitmap, jpeg, etc)
[1]. However, I have not found a way to do this with Yahoo! Boss. Is this
possible?

I've tried tacking on a format parameter to the end of a search, but the results
are the same: unfiltered. For example, executing an image search of "dog" with
the following url:

http://boss.yahooapis.com/ysearch/images/v1/dog?start=0&count=50&lang=en®ion=\
us&appid=<appid>

returns the same results as the following url:


http://boss.yahooapis.com/ysearch/images/v1/dog?start=0&count=50&lang=en®ion=\
us&appid=<appid>&format=gif

I also haven't seen this documented anywhere.

Thank you.

[1] http://developer.yahoo.com/search/image/V1/imageSearch.html

#2853

From: "bossusergroupjustin" <bossusergroupjustin@...>
Date: Thu Dec 16, 2010 2:36 pm
Subject: Re: Specifying the kind of image file to search for

bossusergrou...

Hi Jason

The BOSS web api has the 'type' parameter which does what you are looking for.
However, the image api doesn't support this.

Justin
BOSS User Group Support Team

--- In ysearchboss@yahoogroups.com, "jtothecro" <jasoncrowder@...> wrote:
>
> With the deprecated Yahoo! Image Search api, when searching for images you
could specify the type of image you would like to search for (png, bitmap, jpeg,
etc) [1]. However, I have not found a way to do this with Yahoo! Boss. Is this
possible?
>
> I've tried tacking on a format parameter to the end of a search, but the
results are the same: unfiltered. For example, executing an image search of
"dog" with the following url:
>
>
http://boss.yahooapis.com/ysearch/images/v1/dog?start=0&count=50&lang=en®ion=\
us&appid=<appid>
>
> returns the same results as the following url:
>
>
>
http://boss.yahooapis.com/ysearch/images/v1/dog?start=0&count=50&lang=en®ion=\
us&appid=<appid>&format=gif
>
> I also haven't seen this documented anywhere.
>
> Thank you.
>
> [1] http://developer.yahoo.com/search/image/V1/imageSearch.html
>

#2854

From: "Nadal..." <chinaptb@...>
Date: Fri Dec 31, 2010 3:46 pm
Subject: hey Good Day!!! how've you been!?!?

chinaptb

What's up, this is very fascinating! If you want to lose weight, improve your health, increase your energy or
simply look your best, http://plugin.name/8/yUEUp4 !! can help you achieve your goals.

#2855

From: "gambizness" <jasongambert@...>
Date: Sun Jan 2, 2011 8:38 am
Subject: What steps you need to take in order to have a working Boss.

gambizness

After you have succesfully applied for a "Boss" Application ID do the following
to have your working search engine.

Step 1.)

#2856

From: "hdemazancourt" <hugues@...>
Date: Mon Jan 3, 2011 6:08 pm
Subject: Difference between Yahoo Search and BOSS

hdemazancourt

Hi all, and best wishes for 2011

We are experiencing an increasing  difference in search results between Y!
Search (French version) and BOSS. This has always been more or less the case,
but results were similar.
Now, it is as if BOSS index only had "old" pages: relevant recent pages (that is
less than 2 months) are almost absent from BOSS results.

Are other users experiencing the same behaviour ?

Has this something to do with the Bing/V2 migration ? Any update from Yahoo on
that point ?

Best regards

Hugues

#2857

From: Ashim Chhabra <achhabra@...>
Date: Mon Jan 3, 2011 8:50 pm
Subject: Re: Difference between Yahoo Search and BOSS

ashim

Hi Hugues,

We're testing traffic with Bing results for global markets. BOSS v1 will continue to use Yahoo's search technology 100%, but a percentage of Y! Search global front ends will be fetching results from Bing. This is likely causing the behavior difference you are noticing. Note US/Canada Y! Search front end is already 100% integrated with Bing serving the "core" results (since August).

Thanks,

Ashim

On Jan 3, 2011, at 10:08 AM, hdemazancourt wrote:

Hi all, and best wishes for 2011

We are experiencing an increasing difference in search results between Y! Search (French version) and BOSS. This has always been more or less the case, but results were similar.
Now, it is as if BOSS index only had "old" pages: relevant recent pages (that is less than 2 months) are almost absent from BOSS results.

Are other users experiencing the same behaviour ?

Has this something to do with the Bing/V2 migration ? Any update from Yahoo on that point ?

Best regards

Hugues

#2858

From: "ddgray" <ddgray@...>
Date: Tue Jan 4, 2011 1:15 am
Subject: Yahoo! - 999 Unable to process request at this time -- error 999

ddgray

BOSS Team,

We are receiving error 999 currently.   How can I get this resolved?  We have
been using BOSS for well over a year.

Thanks

David