How to Install and Uninstall httpcomponents-core.noarch Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: November 27,2024

1. Install "httpcomponents-core.noarch" package

This guide let you learn how to install httpcomponents-core.noarch on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                httpcomponents-core.noarch
            
                    
    
    Copied

2. Uninstall "httpcomponents-core.noarch" package

This guide let you learn how to uninstall httpcomponents-core.noarch on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                httpcomponents-core.noarch
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the httpcomponents-core.noarch package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 0:04:58 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : httpcomponents-core
Version : 4.4.13
Release : 7.el9
Architecture : noarch
Size : 635 k
Source : httpcomponents-core-4.4.13-7.el9.src.rpm
Repository : ubi-9-appstream-rpms
Summary : Set of low level Java HTTP transport components for HTTP services
URL : http://hc.apache.org/
License : ASL 2.0
Description : HttpCore is a set of low level HTTP transport components that can be
: used to build custom client and server side HTTP services with a
: minimal footprint. HttpCore supports two I/O models: blocking I/O
: model based on the classic Java I/O and non-blocking, event driven I/O
: model based on Java NIO.
:
: The blocking I/O model may be more appropriate for data intensive, low
: latency scenarios, whereas the non-blocking model may be more
: appropriate for high latency scenarios where raw data throughput is
: less important than the ability to handle thousands of simultaneous
: HTTP connections in a resource efficient manner.