How to Install and Uninstall perl-AnyEvent-HTTP Package on openSUSE Leap

Last updated: May 18,2024

1. Install "perl-AnyEvent-HTTP" package

Please follow the step by step instructions below to install perl-AnyEvent-HTTP on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                perl-AnyEvent-HTTP
            
                    
    
    Copied

2. Uninstall "perl-AnyEvent-HTTP" package

This guide covers the steps necessary to uninstall perl-AnyEvent-HTTP on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                perl-AnyEvent-HTTP
            
                    
    
    Copied

3. Information about the perl-AnyEvent-HTTP package on openSUSE Leap

Information for package perl-AnyEvent-HTTP:
-------------------------------------------
Repository : Main Repository
Name : perl-AnyEvent-HTTP
Version : 2.25-bp155.2.8
Arch : noarch
Vendor : openSUSE
Installed Size : 101.5 KiB
Installed : No
Status : not installed
Source package : perl-AnyEvent-HTTP-2.25-bp155.2.8.src
Upstream URL : https://metacpan.org/release/AnyEvent-HTTP
Summary : Simple but non-blocking HTTP/HTTPS client
Description :
This module is an AnyEvent user, you need to make sure that you use and run
a supported event loop.
This module implements a simple, stateless and non-blocking HTTP client. It
supports GET, POST and other request methods, cookies and more, all on a
very low level. It can follow redirects, supports proxies, and
automatically limits the number of connections to the values specified in
the RFC.
It should generally be a "good client" that is enough for most HTTP tasks.
Simple tasks should be simple, but complex tasks should still be possible
as the user retains control over request and response headers.
The caller is responsible for authentication management, cookies (if the
simplistic implementation in this module doesn't suffice), referer and
other high-level protocol details for which this module offers only limited
support.