I would like a web service to post OpenSearch hits to, for metrics.

RESOLVED FIXED

Status

RESOLVED FIXED
8 years ago
8 years ago

People

(Reporter: bwinton, Assigned: gozer)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

I suspect I'll just be sending one of the names in this list:
["Wikipedia (en)", "Bing", "eBay", "Creative Commons", "Answers.com", "Amazon.com", "Yahoo", "Google"]
but accepting any string (for extensibility) seems like a good idea.

Thanks,
Blake.
(Assignee)

Comment 1

8 years ago
SOomething like :

https://opensearch.live.mozillamessaging.com/search/google?q=[xxxx]
 =>
http://www.googe.com/search?q=[xxxx]

And really, internally we'd have mappings like:

/google => http://www.google.com/search

And pass everything else along, right ??
we decided to take pings with a get parameter, return 206, use access logs to store metrics, everyone wins!
(Assignee)

Comment 3

8 years ago
(In reply to comment #2)
> we decided to take pings with a get parameter, return 206, use access logs to
> store metrics, everyone wins!

Can we agree on the format of these pings ?
(Reporter)

Comment 4

8 years ago
Sure,  Pick something, and I'll code that up.

(I figured it would be along the lines of http://…/…?provider=<XXX> )

Later,
Blake.
(Reporter)

Comment 6

8 years ago
(I asked Sancus, and he said he can't do it, so I'm assigning it to you so that it doesn't get lost.  Also, we're hoping to release the add-on next week, so getting this up soon would be good.)
Assignee: nobody → gozer
Status: NEW → ASSIGNED
(Assignee)

Comment 7

8 years ago
$> lwp-request -m GET -esS http://opensearch.live.mozillamessaging.com/search?provider=google
GET http://opensearch.live.mozillamessaging.com/search?provider=google --> 204 No Content
Connection: close
Date: Thu, 10 Feb 2011 21:17:28 GMT
Via: 1.1 varnish
Age: 0
Server: Apache/2.2.3 (CentOS)
Content-Length: 0
Content-Type: text/plain; charset=UTF-8
Client-Date: Thu, 10 Feb 2011 21:17:28 GMT
Client-Peer: 63.245.221.10:80
Client-Response-Num: 1
X-Varnish: 2943614467
Status: ASSIGNED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.