How to Install and Uninstall libhttp_parser2_9-32bit Package on openSuSE Tumbleweed
Last updated: November 22,2024
Deprecated! Installation of this package may no longer be supported.
1. Install "libhttp_parser2_9-32bit" package
Please follow the steps below to install libhttp_parser2_9-32bit on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
libhttp_parser2_9-32bit
Copied
2. Uninstall "libhttp_parser2_9-32bit" package
Please follow the steps below to uninstall libhttp_parser2_9-32bit on openSuSE Tumbleweed:
$
sudo zypper remove
libhttp_parser2_9-32bit
Copied
3. Information about the libhttp_parser2_9-32bit package on openSuSE Tumbleweed
Information for package libhttp_parser2_9-32bit:
------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : libhttp_parser2_9-32bit
Version : 2.9.4-1.7
Arch : x86_64
Vendor : openSUSE
Installed Size : 37,5 KiB
Installed : No
Status : not installed
Source package : http-parser-2.9.4-1.7.src
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 : openSUSE-Tumbleweed-Oss
Name : libhttp_parser2_9-32bit
Version : 2.9.4-1.7
Arch : x86_64
Vendor : openSUSE
Installed Size : 37,5 KiB
Installed : No
Status : not installed
Source package : http-parser-2.9.4-1.7.src
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).