Closed Bug 32406 Opened 24 years ago Closed 24 years ago

Lycos Search not using correct URLs

Categories

(SeaMonkey :: Search, defect, P3)

All
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jpranevich, Assigned: mozilla)

Details

I'm walking a fine line between Mozilla user and Lycos employee here, but since
I want to be able to do Lycos searches using the Mozilla browser, I think I'm
justified in reporting this.

The interface currently used for the Lycos Search component of Mozilla is
www-partner.lycos.com with a &part=MACOS. I don't know how you got that URL but
that's not a public interface (but yes, it works) and you probably shouldn't
spoof someone else's partner tag anyway.

A more correct URL would be:

http://www.lycos.com/srch/?query=keywords&loc=mozilla

Or something to that effect, using the "public" interface. If you're trying to
do something special by using or if there is a specific reason that I'm not
aware of for using that interface, let me know and I'll see if we have similar
functionality somewhere else or at least give you appropiate tagging...

(This message was written completely of my own free will and does not reflect on
my status as a Lycos employee or imply any connections between Lycos and
Mozilla, Netscape, AOL, or anyone else. It's just me, damnit.)
We should be using our own search string.
This way we get created for the abundant mozilla searches
rather than the mac getting all the credit unless it screws up
the sherlock files.
Assignee: matt → rjc
jpranevich, I appreciate you bringing this to our attention.

Currently, Lycos is not available in Mozilla. (Note: on Mac, we use all Sherock 
files, including those including with Mac OS.)

We'll be making deals with various search engines, and they'll be providing us 
with Sherlock files to use, so this issue will be resolved appropriately.

Marking this bug FIXED.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
marking VERIFIED
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.