How to Install and Uninstall ghc-http-client-restricted.x86_64 Package on Fedora 36

Last updated: January 10,2025

1. Install "ghc-http-client-restricted.x86_64" package

Here is a brief guide to show you how to install ghc-http-client-restricted.x86_64 on Fedora 36


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                ghc-http-client-restricted.x86_64
            
                    
    
    Copied

2. Uninstall "ghc-http-client-restricted.x86_64" package

Learn how to uninstall ghc-http-client-restricted.x86_64 on Fedora 36:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                ghc-http-client-restricted.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the ghc-http-client-restricted.x86_64 package on Fedora 36

Last metadata expiration check: 1:27:56 ago on Thu Sep 8 02:05:26 2022.
Available Packages
Name : ghc-http-client-restricted
Version : 0.0.3
Release : 6.fc36
Architecture : x86_64
Size : 30 k
Source : ghc-http-client-restricted-0.0.3-6.fc36.src.rpm
Repository : fedora
Summary : Restricting the servers that http-client will use
URL : https://hackage.haskell.org/package/http-client-restricted
License : MIT
Description : Addition to the http-client and http-client-tls libraries, that restricts the
: HTTP servers that can be used.
:
: This is useful when a security policy needs to eg, prevent connections to HTTP
: servers on localhost or a local network, or only allow connections to a
: specific HTTP server.
:
: It handles restricting redirects as well as the initial HTTP connection, and it
: also guards against DNS poisoning attacks.