Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cabal install fails to update with parse error #1696

Closed
tim-m89 opened this issue Feb 21, 2014 · 1 comment
Closed

Cabal install fails to update with parse error #1696

tim-m89 opened this issue Feb 21, 2014 · 1 comment

Comments

@tim-m89
Copy link

tim-m89 commented Feb 21, 2014

C:\Documents and Settings\Tim>cabal update
Downloading the latest package list from hackage.haskell.org
Warning: http error: Network.Browser.request: Error raised ErrorParse
"parseResponseHead Response status line parse failure: <html>\r\n"
cabal: Network.Browser.request: Error raised ErrorParse "parseResponseHead
Response status line parse failure: <html>\r\n"

Issue is present on a windows xp machine with fresh install of the latest haskell platform. Remains present when cabal install is replaced with the latest version:

C:\Documents and Settings\Tim>cabal --version
cabal-install version 1.18.0.2
using version 1.18.1 of the Cabal library

This computer has no issues accessing the internet though any other software:

C:\Documents and Settings\Tim>ping google.com

Pinging google.com [202.124.127.26] with 32 bytes of data:

Reply from 202.124.127.26: bytes=32 time=2ms TTL=59
Reply from 202.124.127.26: bytes=32 time=1ms TTL=59

Ping statistics for 202.124.127.26:
    Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms
Control-C

And does not use any proxy settings.

@tim-m89 tim-m89 closed this as completed Feb 21, 2014
@tim-m89 tim-m89 reopened this Feb 21, 2014
@ttuegel
Copy link
Member

ttuegel commented Feb 28, 2015

Please re-open if this is still an issue with cabal-install-1.22.

@ttuegel ttuegel closed this as completed Feb 28, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants