lynx/google error - Help

This is a discussion on lynx/google error - Help ; Hello all, I'm pretty new to linux, and I have a Q about where to post my Q. I was using lynx on a gnome terminal with irssi in another tab. In lynx I g. google.com and got a bad ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: lynx/google error

  1. lynx/google error

    Hello all,
    I'm pretty new to linux, and I have a Q about where to post my Q. I was
    using lynx on a gnome terminal with irssi in another tab. In lynx I g.
    google.com and got a bad request error;

    400 Bad
    Request (p1
    of 4)

    Google
    Error

    Bad Request

    Your client has issued a malformed or illegal request. Please see
    Google's Terms of Service posted at
    http://www.google.com/terms_of_service.html

    We have encountered an error while processing your request. If you
    would like to provide us with information about this error, please
    report your problem. In your email, please send us the entire code
    displayed below. Please also send us any information you may know
    about how you are performing your Google searches-- for example, "I'm
    using the Opera browser on Linux to do searches from home. My
    Internet access is through a dial-up account I have with the FooCorp
    ISP." or "I'm using the Konqueror browser on Linux to search from my
    job at myFoo.com. My machine's IP address is 10.20.30.40, but all of
    myFoo's web traffic goes through some kind of proxy server whose IP
    address is 10.11.12.13." (If you don't know any information like
    this, that's OK. But this kind of information can help us track down
    problems, so please tell us what you can.)

    We will use all this information to diagnose the problem, and we'll
    hopefully have you back up and searching with Google again quickly!

    Please note that although we read all the email we receive, we are
    not always able to send a personal response to each and every email.
    So don't despair if you don't hear back from us!
    400
    Bad
    Request
    (p2
    of
    4)
    Also note that if you do not send us the entire code below, we will
    not be able to help you.

    Best wishes,
    The Google Team


    /+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/
    mgmwyOgGyQ8_1WiEit0IN2lXEa4sRya4EGD-weBX7JfnSgBZH
    s4quFpM6UJzt1-dw9XOs4brqOyD9MzGGPl5R1Tsj7H3uWatFa
    4O9Zuxs7JVaqfUMsRhalkEfUUj9h7kKahDfKdggHldPoAYEWd
    8QXf5gtyaDkt6FOim0NTx0XHlrhtIkaguzYjjt-cTziby-snn
    BYHFQyC7vFOBkVMeyGpM4IS0JU0VLf3Woj0uduSj9hB0IqVrE
    TdwWi32npPFjVeur73TnUPmVoVMEzoqMGV0bb2pZ44yfZv_mz
    bG-_504rqZZYEPh4PLqjM6cACQ837c5cusAhXjOEM1zsAPigB
    hhecxG-H7dHi_ZMgMPifnkJlHmBWYdIapSlWKc1m8fZv_mzbG
    -_504rqZZYEPh4IV2hYRJGC1K2Ve4_0rYBGj9hB0IqVrEXdFN
    fCflpIX5yGD3o4Xro5WTeAw4NBd9oflL8u21_Qbd0U18J-Wkh
    fnIYPejheujlZN4DDg0F32VhiVBg7hbNwd1SYUe_Nb_H2b_5s
    2xvv-dOK6mWWBD4efG_7TmGUKm1YeV61SRk66UW3pCnIZJg53
    RTXwn5aSFxBUhK2jgzNsDt9ZsEQlss76yecFgcVDICKxl-zvV
    CDRKpb5-STOUUbUy95qWKpOgwAytm7KplSyBbgIZSdjZT4XqM
    QLg4FvvIwCmmP4StfDyDVhs_Dx4qGqJpq325D4xABhhecxG-H
    7EVHIfp89TQ5GEYFexGiai6vhsgSzGafrsXh122O1oo43cFot
    9p6TxavhsgSzGafrNaKdvZN-yfn7nEpUboi51n2b_5s2xvv-8
    xwSofzuI1Pb6ykneMJeQxeoxAuDgW-8HT-4ZkTHCqedYQgz8B
    qD-32b_5s2xvv-7CyOx695POLvhSRYbq3uMABhhecxG-H7_j8
    m9vMegfc3cFot9p6TxROUk8WxQnho-snnBYHFQyA-3AX56xlr
    ySSRoYsulasyOhhPSZdSC0qvaGGnZonxSbNnb17y9MgviV_Dy
    C-6aMbpaDhi5Dgc0Q4OMt6x9KbRumEy3tY4vJlGEYFexGiai4
    1Xrq-9051DC7r9QE3g2FbezHyaVf1YMYYfZVIxAihXCrcXLHG
    XaP83cFot9p6TxY1Xrq-9051DC7r9QE3g2FbezHyaVf1YMYYf
    ZVIxAihX0iNCNIAntXeEiNVp2kMQyfrJ5wWBxUMgu7xTgZFTH
    shxnqU4p8GzqH-toVWWFT-1lN_KlFNiApcnJwZU3EKYLBTopt
    DU8dFxpxv3Hbbv7tb8uYszdjm9kGO__Az3D4ZCfZv_mzbG-_5
    04rqZZYEPh5QgAjsV6ch5eRy3MtL5DPHYwVtFr39DBru8U4GR
    Ux7IcZ6lOKfBs6h_raFVlhU_tZuvyaYEY-dMMPSqXBs1vvN9m
    _-bNsb7_qArkapPHNNif9P0GhO2a_CaTLZT-RRQwgVzNqj0vS
    uHx-8igo0bFB4WyG5Brj5tELNnb17y9MgvXcOGyUoUlwgX3Zx
    h9X1-lxlr0Hwkcqcnd0U18J-WkhfnIYPejheujrH4UTBQlfIa
    hXdpaaDjk2ZZ0TVG6pFMOh_h2XkEtmCKN3BaLfaek8WNV66vv
    dOdQwu6_UBN4NhW3sx8mlX9WDFL9yMU5qmNCppE1OyGutM28A
    8KkCZ7xpVgqaS_FGAL87u8U4GRUx7IiZQponadWzzjRjxRpji
    OgJ0Xg-4lk4cVd0U18J-WkhfnIYPejheujrH4UTBQlfIahXdp
    aaDjk2bEJjGUriunyYXBue2EW3EUFOim0NTx0XGnG_cdtu_u1
    vy5izN2Ob2QZIhZW_XSTkx9m_-bNsb7_qArkapPHNNif9P0Gh
    O2a_CaTLZT-RRQwvpw-3HFgONJd0U18J-WkhfnIYPejheujrH
    4UTBQlfIahXdpaaDjk2a2W3iayN7BXISI1WnaQxDJRhGBXsRo
    mouNV66vvdOdQwu6_UBN4NhW3sx8mlX9WDELp8j1eyqwjy-TS
    0-CU24KAGGF5zEb4fvuue4u1_BYbUFWZis8GGZ2n8nOYCcWps
    PVot9spZ4983bCL5jdxbAKAGGF5zEb4fvseobbKGN7j8IiwER
    pzbkG1wybLa1LhXRCllliotc4nfrJ5wWBxUMgu7xTgZFTHsiJ
    lCmidp1bPL2MbgkWRTM6NXYf4A3L_EN9m_-bNsb7_ljDoPLFJ
    TaA-snnBYHFQyA6G1CvwxOcTq-685Dmz40HyzKrXh5jS1mEN2
    QQUklBKzmLx2Pdo49GJA0UPxrwejjXsRKYzO63QMOFzAqhwRZ
    dhDdkEFJJQSunEQdI9oj92jdwWi32npPFnUb59C915mnV88EF
    K-LVCLNnb17y9Mgv3VK34vbu_GbVupZ7jgk9fZIjm9GsFa97F
    6jEC4OBb7yr7YdttIy60n2b_5s2xvv-an6bTThVPI4PaIy4dy
    7-ZxToptDU8dFx0jO0OxkaCYxxTd6ne-H-2QBhhecxG-H7S9V
    tQ0qH4Ww8p9Sm8gr9lLNnb17y9Mgvz7d8jcKpLZ_Wmu9T9zCM
    Fn2b_5s2xvv-MEYzMeB28AfrZfko07NuNCnrr3BZNz0es2dvX
    vL0yC_yg__yOZ4_AhXeeBB29awRN3BaLfaek8UdUW6uw_BWAF
    GzaIeOhyDls2dvXvL0yC_sHk_KOhoJVNpC8v-8gYwzAGGF5zE
    b4fuQNlbuJXF2LYIGv9GRa_4rN3BaLfaek8UwI0844aF27y1t
    -jFHmEznfZv_mzbG-_49J2EV_Q2RjH_588YSHnCOd0U18J-Wk
    hdcXDNroNFDAUZxYwrS0KESbGky7JRmZ8EU6KbQ1PHRcbMEHU
    fv6y9QeXmvKWPLvhY3cFot9p6TxaRlL5h6NhVP_ncMkzfphTE
    dP9sT0WVrd6Rt70OCq6_5NrGv2JTLrQq9K2n-4OOt7DXwEIWr
    IKnU8A5EBJ_Nl635o6GVuCQnjysbLgG_cn7_m0-cCVjmI1kAY
    YXnMRvh-xxT98pTgDzzYREm-3vcgmDwB9wcDU480fu6kgVUq5
    43hP7oV8OpjWzBCOgYgF_hwQyMhyZvs0oPx4Bw2PcZaK9AWXw
    rHLO1gjLz95AlT0H-P1EDUDycAt89DIER-_HW3Bte_ZtpPAV6
    8QWzZ_sBx-XZy-Yvomwv-N2HPAkwjviMoApSF3Sa3S_vfBA2c
    oDt4OxHDcfDneTDRAiaUOcHAz-JXsPWZm3HWK4zaY6fX9IBA0 P2onqHOMHMqKEn
    +/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+



    I tried the bookmark , same thing.
    I closed the terminal, restarted it, same thing. I can still get to google
    with graphical browser, and using lynx in console. I suspect irc or irssi
    did something, and I'm not sure where to post. I sent email to google
    security, no response yet, and posted to google search user group. Any
    advice where to go for help?
    Thanks.

    --
    jeff

  2. Re: lynx/google error

    Hello, look below for my answer..

    On Tue, 18 Mar 2008 05:09:10 +0000, jeff pugh wrote:

    > Hello all,
    > I'm pretty new to linux, and I have a Q about where to post my Q. I was
    > using lynx on a gnome terminal with irssi in another tab. In lynx I g.
    > google.com and got a bad request error;
    >
    > 400 Bad
    > Request
    > (p1
    > of 4)


    [snip]

    >
    > I tried the bookmark , same thing.
    > I closed the terminal, restarted it, same thing. I can still get to
    > google with graphical browser, and using lynx in console. I suspect irc
    > or irssi did something, and I'm not sure where to post. I sent email to
    > google security, no response yet, and posted to google search user
    > group. Any advice where to go for help?
    > Thanks.


    What you have in another tab of the terminal window, does not matter.
    It is lynx sending something to google that google does not like.

    When you activate a link, the browser is supposed to send the string that
    is encoded with the link. Even if it is not shown on your screen, it is
    there in the document you are currently viewing. If this string is
    faulty, the problem is with the authors of the page you were currently
    viewing when you activated the link.

    Some links are different, though, such as the "search" button on the
    google search page. When that one is activated, the browser is supposed
    to compose a request incorporating whatever you have written in the
    search field. However, no matter what you type in the search field, the
    browser is supposed to know how to transform it so that is does not
    create problems. For instance, if you type the '<' character in the
    search field, the browser should send '<' instead of that character.

    If this goes wrong, it is lynx that is at fault.

    But the web has evolved and the pages have become more sophisticated.
    Today many submit buttons require the browser to run small pieces of
    program code that are included in the page you are viewing (but not shown
    on the screen). Browsers that do not support such execution are safer,
    but frustrating when the page does not work as expected. I do not know if
    google has switched to rely on such javascript support. I think lynx
    never had it.

    As far as I can remember, lynx is no longer being developed. Most people
    has switched to one of a range of other similar text-only browsers, like
    "links", "w3m", and "elinks". Hm, I googled around a little, and I may be
    mistaken, it appears that lynx is still being developed. Yet, the others
    in the list were developed, among other things because lynx did not
    support frames, tables, and javascript. One old roundup I found said
    that elink was the only text-mode browser to support javascript. However,
    elinks did not support utf8 (the most common way to represent non-english
    characters on linux).

    I guess you will not hear from Google soon, the lynx user base being too
    small. If they spot an error on their stuff, of course they fix it, but
    otherwise you are left to yourself and people like me.

    Others may know more about specific problems with lynx and google. I
    would either not bother too much with lynx, or I would try to find out
    what exactly your browser is sending. My favorite method is to snoop on
    the wire, using wireshark. Wireshark is a program you can intall on your
    linux computer. If you have fedora or similar, try "yum install
    wireshark", if you have debian or ubuntu, try "aptitude install wireshark"
    Fire it up, figure out how to get it start capturing the network traffic,
    then start your browser and use it until the error appears. Then switch
    back to the wireshark window. There will be tons of data you most likely
    don't understand. Look for lines labeled with HTTP. Click on them in
    turn. In the lower pane, the contents of each datagram can be inspected.
    Look among the first ones in each connection, one having "GET" or "POST"
    prominently. Write down (strangely wireshark does not support cut &
    paste), and post to the groups to ask what is wrong with it.

    Regards


  3. Re: lynx/google error

    On Fri, 18 Apr 2008 12:14:41 +0000, Enrique Perez-Terron wrote:

    > Hello, look below for my answer..
    >
    > On Tue, 18 Mar 2008 05:09:10 +0000, jeff pugh wrote:
    >
    >> Hello all,
    >> I'm pretty new to linux, and I have a Q about where to post my Q. I was
    >> using lynx on a gnome terminal with irssi in another tab. In lynx I g.
    >> google.com and got a bad request error;
    >>
    >> 400 Bad
    >> Request
    >> (p1
    >> of 4)

    >
    > [snip]


    I just saw on another thread that google just does not like lynx. They
    said remove the browser identification, -useragent=STRING.

    Since I do not have lynx installed any more, I cannot test it.

    The docs say you get a warning if the string does not contain "Lynx".

    Regard.

+ Reply to Thread