How to Install and Uninstall libhttp_parser2_7_1-32bit Package on openSUSE Leap
Last updated: November 23,2024
1. Install "libhttp_parser2_7_1-32bit" package
In this section, we are going to explain the necessary steps to install libhttp_parser2_7_1-32bit on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
libhttp_parser2_7_1-32bit
Copied
2. Uninstall "libhttp_parser2_7_1-32bit" package
Please follow the guidelines below to uninstall libhttp_parser2_7_1-32bit on openSUSE Leap:
$
sudo zypper remove
libhttp_parser2_7_1-32bit
Copied
3. Information about the libhttp_parser2_7_1-32bit package on openSUSE Leap
Information for package libhttp_parser2_7_1-32bit:
--------------------------------------------------
Repository : Main Repository
Name : libhttp_parser2_7_1-32bit
Version : 2.7.1-4.2.2
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 29.4 KiB
Installed : No
Status : not installed
Source package : http-parser-2.7.1-4.2.2.src
Upstream URL : https://github.com/nodejs/http-parser
Summary : HTTP request/response parser for C
Description :
This is a parser for HTTP messages written in C. It parses both
requests and responses. The parser is designed to be used in
performance HTTP applications. It does not make any syscalls nor
allocations, it does not buffer data, it can be interrupted at
anytime. Depending on your architecture, it only requires about 40
bytes of data per message stream (in a web server that is per
connection).
--------------------------------------------------
Repository : Main Repository
Name : libhttp_parser2_7_1-32bit
Version : 2.7.1-4.2.2
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 29.4 KiB
Installed : No
Status : not installed
Source package : http-parser-2.7.1-4.2.2.src
Upstream URL : https://github.com/nodejs/http-parser
Summary : HTTP request/response parser for C
Description :
This is a parser for HTTP messages written in C. It parses both
requests and responses. The parser is designed to be used in
performance HTTP applications. It does not make any syscalls nor
allocations, it does not buffer data, it can be interrupted at
anytime. Depending on your architecture, it only requires about 40
bytes of data per message stream (in a web server that is per
connection).