Find the answer to your Linux question:
Results 1 to 6 of 6
Hello all, I've fiddled with linux a little since about 1998, starting peanut. That didn't last long. Then a couple of years ago with suse and ubuntu, better but still ...
  1. #1
    Just Joined!
    Join Date
    Mar 2008
    Posts
    6

    Question lynx/googl error



    Hello all,
    I've fiddled with linux a little since about 1998, starting peanut. That didn't last long. Then a couple of years ago with suse and ubuntu, better but still no sound, so back to xp. Now about a month ago xp died and I don't know what went with the install disk. So I did some reading and got myself a debian netinst iso, and I'm very pleased that I even have sound, very painless install. I've got a problem with lynx or GNOME Terminal 2.14.2 or google though. First I want to get my terminology right. OK when I'm using GNOME Terminal 2.14.2 or konsole that is a terminal, right? And when I ctrl alt f1 that is the console, ? Am I saying this right?

    Anyway, I was using (Lynx Version 2.8.5rel.1) on a GNOME Terminal 2.14.2, under Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1). I'm using a dsl connection with at&t. I havn't had a problem getting to google.com before.but now, when I 'g'oto "google.com" I get the error message below, I get the same thing trying to use the bookmark. I can still use my graphical browser and get to google.com. And If I ctrl alt f1 , console? I can use lynx from there and get to google.com this it the only web page that does this and it wasn't a problem before. I really need my google, and I'm trying to learn to use less graphical stuff . Any help will be much welcomed. The error I got is below.
    Thanks Jeff Pugh.



    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
    +/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+/+


    Question

  2. #2
    Linux Engineer jledhead's Avatar
    Join Date
    Oct 2004
    Location
    North Carolina
    Posts
    1,077
    you could try
    #apt-get install elinks

    slightly more featured text based browser

    not sure what you problem could be. at a commmand line if you type
    #lynx Google
    do you get that error every time? are you behind a proxy?

    try elinks, it works very similar

  3. #3
    Linux Guru
    Join Date
    Oct 2007
    Location
    Tucson AZ
    Posts
    1,934
    Tried lynx on my suse 9.2 (google.com) and got the same error msg you did. Was able to connect with other sites using lynx. Used w3m and elinks and was able to connect to google. Used lynx on Slackware 11.0 and connected to google. ???

  4. #4
    Just Joined!
    Join Date
    Mar 2008
    Posts
    6

    w3m

    OK I'm giving this w3m a whirl, so far so good. I guess I could have tried it to begin with since it came with
    debian. I was surpresed when the editor opened. I've never posted using a text browser before. Pretty cool. I think I
    can get used to this. Thanks for the input folks. I'm sure you'll be hearing from me again.

  5. #5
    Just Joined! Agnot's Avatar
    Join Date
    Mar 2008
    Posts
    5

    Post

    This is a known problem in lynx 2.8.5-2, which was in sarge and still, etch, by my repository. lynx-cur, which is 2.8.7dev, works without any development issues for me. Either 2.8.6 or 2.8.5-4 will also fix it if you can find and install them.

    I think it was a discrepancy between lynx and google in handling put and get methods.

    Bug#404957: lynx: google reports malformed browser request

  6. #6
    Linux Engineer rcgreen's Avatar
    Join Date
    May 2006
    Location
    the hills
    Posts
    1,112
    Cause: Some Linux distributions ship with a large /etc/mailcap or ~/.mailcap file that Lynx is using to send a huge Accept: header and google doesn’t like it.

    Fix: In /etc/lynx.cfg, edit

    "GLOBAL_MAILCAP:/etc/mailcap" to "GLOBAL_MAILCAP:/dev/null"
    or
    "PERSONAL_MAILCAP:~/.mailcap" to "PERSONAL_MAILCAP:/dev/null"

    as appropriate (depending on which mailcap file is causing the grief).
    Not So FAQs » lynx

    I got the same error, but this fixed it.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •