Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • P Pacman
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare
    • Locked Files
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Pacman
  • Pacman
  • Repository
Switch branch/tag
  • pacman
  • lib
  • libalpm
  • dload.h
Find file BlameHistoryPermalink
  • Dave Reisner's avatar
    dload: avoid showing progress bars on some redirects · 132e1ac1
    Dave Reisner authored Jan 15, 2013 and Allan McRae's avatar Allan McRae committed Jan 17, 2013
    
    
    RFC 2616 doesn't forbid a 301 or 302 repsonse from having a body, and
    servers exist in the wild that show this behavior. In order to prevent
    pacman from showing a progress bar when we aren't actually downloading a
    package (and merely following one of these pain in the butt redirects),
    capture the server response code in the response header, rather than
    waiting to peel it off the handle after the download has finished.
    
    Signed-off-by: default avatarDave Reisner <dreisner@archlinux.org>
    Reported-by: default avatarAlexandre Filgueira <alexfilgueira@cinnarch.com>
    Signed-off-by: Allan McRae's avatarAllan McRae <allan@archlinux.org>
    132e1ac1