Http client с linux

HTTPie – A Modern HTTP Client Similar to Curl and Wget Commands

HTTPie (pronounced aitch-tee-tee-pie) is a cURL-like, modern, user-friendly, and cross-platform command line HTTP client written in Python. It is designed to make CLI interaction with web services easy and as user-friendly as possible.

HTTPie – A Command Line HTTP Client

It has a simple http command that enables users to send arbitrary HTTP requests using a straightforward and natural syntax. It is used primarily for testing, trouble-free debugging, and mainly interacting with HTTP servers, web services and RESTful APIs.

• HTTPie comes with an intuitive UI and supports JSON.
• Expressive and intuitive command syntax.
• Syntax highlighting, formatted and colorized terminal output.
• HTTPS, proxies, and authentication support.
• Support for forms and file uploads.
• Support for arbitrary request data and headers.
• Wget-like downloads and extensions.
• Supports ython 2.7 and 3.x.

In this article, we will show how to install and use httpie with some basic examples in Linux.

How to Install and Use HTTPie in Linux

Most Linux distributions provide a HTTPie package that can be easily installed using the default system package manager, for example:

Once installed, the syntax for using httpie is:

The most basic usage of httpie is to provide it a URL as an argument:

Basic HTTPie Usage

Now let’s see some basic usage of httpie command with examples.

Send a HTTP Method

You can send a HTTP method in the request, for example, we will send the GET method which is used to request data from a specified resource. Note that the name of the HTTP method comes right before the URL argument.

Send GET HTTP Method

Upload a File

This example shows how to upload a file to transfer.sh using input redirection.

Download a File

You can download a file as shown.

Submit a Form

You can also submit data to a form as shown.

View Request Details

To see the request that is being sent, use -v option, for example.

View HTTP Request Details

Basic HTTP Auth

HTTPie also supports basic HTTP authentication from the CLI in the form:

Custom HTTP Headers

You can also define custom HTTP headers in using the Header:Value notation. We can test this using the following URL, which returns headers. Here, we have defined a custom User-Agent called ‘strong>TEST 1.0’:

Custom HTTP Headers

See a complete list of usage options by running.

You can find more usage examples from the HTTPie Github repository: https://github.com/jakubroztocil/httpie.

HTTPie is a cURL-like, modern, user-friendly command line HTTP client with simple and natural syntax, and displays colorized output. In this article, we have shown how to install and use httpie in Linux. If you have any questions, reach us via the comment form below.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

We are thankful for your never ending support.

Источник

Best Command Line HTTP Clients for Linux

HTTP clients are utility software that enables you to download files over the Internet. Apart from being able to download files remotely, these command line tools can be used for other tasks such as debugging and interacting with web servers.

Today, check out our list of the best HTTP clients created for use in the Linux Command Line.

1. HTTPie

HTTPie is an open source command line HTTP client for interacting with HTTP servers, web services, and RESTful APIs. HTTPie pronounced “aych-tee-tee-pie” and its aim is to simplify human interaction with web services via the command line, so most people use it for Wget-like downloads.

Its other features include a type-based colorized syntax, custom headers, persistent sessions, support for plugins, built-in support for JSON, etc.

HTTPie Linux HTTP Client

2. HTTP Prompt 2

HTTP Prompt is an interactive command-line HTTP client built on prompt_toolkit and HTTPie with 20+ themes. Its feature highlights include auto-complete, syntax highlighting, auto cookies, Unix-like pipelines, compatibility with HTTpie, http-prompt persists in-between sessions, and OpenAPI/Swagger integration.

HTTP Prompt – Command Line HTTP Client for Linux

3. Curl

Curl is an open source command line utility and library for transferring files over a network using URL syntax over any of several supported protocols including SCP, SMTPS, HTTPS, IMAP, LDAP, POP3, etc.

Curl is a very popular utility used in not only terminals and scripts to transfer data but also in routers, printers, tablets, mobile phones, set-top boxes, audio equipment, media players, etc. It has a long feature list which includes support for IPv6 and socks5, custom output results after completion, no URL length limit, asynchronous name resolving.

Curl Query HTTP Headers

4. Wget

Wget is an open source command-line utility for retrieving content from web servers via HTTP proxies as well as HTTP, HTTPS, and FTP protocols. Its function is recursive downloading which entails that it follows the links in HTML pages and create local versions of remote websites.

Wget boasts several features including the ability to function excellently even when your network connection is slow or unstable, support for HTTP proxies and cookies, resume aborted downloads using REST and RANGE APIs, NLS-based message files for different languages, etc.

Wget Download Files to Specific Directory

5. Aria2

Aria2 is a lightweight open source command-line download utility with support for HTTP & HTTPS, FTP & SFTP, Metalink, and BitTorrent. Its features include automatic validation for files like BitTorrent, parallel file downloads from HTTP(S)/(S)FTP and BitTorrent at the same, Ntrc support, disk caching to reduce disk activity, IPv6 support with Happy Eyeballs, etc.

Aria2: Command Line Download Manager for Linux

Are there any awesome command line HTTP clients that are not listed above? Feel free to add your suggestions and reasons in the discussion box below.

If You Appreciate What We Do Here On TecMint, You Should Consider:

TecMint is the fastest growing and most trusted community site for any kind of Linux Articles, Guides and Books on the web. Millions of people visit TecMint! to search or browse the thousands of published articles available FREELY to all.

If you like what you are reading, please consider buying us a coffee ( or 2 ) as a token of appreciation.

We are thankful for your never ending support.

Источник

Клиент-сервер под linux на c++ общение клиентов «все со всеми» с использованием потоков

Начну с того, что была предложена работа на должность программиста с\с++. Задание это название темы.

Полез в интернет, кругом все напичкано чатами и общением по типу клиент-сервер, но увы кода с подобным заданием я так и не нашел. Был примитив типа ЭХО клиент-сервера, который я и решил взять за основу:
Это у нас клиент:

это код сервера:

После всего этого в клиенте нужно отправить сообщение серверу используя функции send или write а на стороне сервера принять сообщение и переотправить его обратно клиенту используя функции read и send.

Вообще есть разные функции отправки и приема, к примеру send и recv вместе с сообщением шлют еще и флаг подтверждения, а функции read и write не требуют подтверждения, то есть сообщение может потерять байты при отправке и это не будет зафиксировано.

Так как сокеты это дуплекс и создавая связь между клиентом и сервером мы не можем писать туда сообщения из других подключенных сокетов, необходимо создать массив со всеми активными сокетами подключенными к серверу. И еще одно замечание очень важное:

Для общения между несколькими сокетами необходимо использовать функцию select, которая выбирает сокет из списка и отсылает ему сообщение, и так далее, пока не закончатся все записанные сокеты

После этого в массив сокетов будет записано правильное значение подключаемого сокета а далее остается лишь перебирать их при рассылке сообщений:

Запишем все это в функцию и создадим отдельный поток:

Что касаемо клиента, то необходимо создать два разных потока для чтения и записи в сокет:

Теперь все работает. Спасибо за снимание. Надеюсь что это пригодится тем, кто так же как и я пытался написать клиент-сервер, но не смог найти нужную информацию в сети.

Источник

Лучшие HTTP-клиенты командной строки для Linux

HTTP-клиенты – это служебное программное обеспечение, позволяющее загружать файлы через Интернет . Помимо возможности удаленной загрузки файлов, эти инструменты командной строки можно использовать для других задач, таких как отладка и взаимодействие с веб-серверами.

Сегодня мы составили список лучших HTTP-клиентов, созданных для использования в командной строке Linux.

1. HTTPie

HTTPie – это HTTP-клиент с открытым исходным кодом для взаимодействия с HTTP-серверами, веб-службами и API-интерфейсами RESTful. HTTPie произносится как «aych-tee-tee-pie», и его цель – упростить взаимодействие человека с веб-сервисами через командную строку, поэтому большинство людей используют его для Wget-подобных загрузок .

Другие его функции включают цветовой синтаксис на основе типов, настраиваемые заголовки, постоянные сеансы, поддержку плагинов, встроенную поддержку JSON и т. Д.

2. HTTP Prompt 2

HTTP Prompt – это интерактивный HTTP-клиент командной строки, созданный на основе prompt_toolkit и HTTPie с более чем 20 темами. Его основные функции включают в себя автоматическое заполнение, подсветку синтаксиса, автоматические куки, Unix-подобные конвейеры, совместимость с HTTpie, http-подсказка сохраняется между сеансами и интеграцию OpenAPI / Swagger.

3. Curl

Curl – это утилита и библиотека командной строки с открытым исходным кодом для передачи файлов по сети с использованием синтаксиса URL по любому из нескольких поддерживаемых протоколов, включая SCP, SMTPS, HTTPS, IMAP, LDAP, POP3 и т. Д.

Curl – очень популярная утилита, используемая не только в терминалах и скриптах для передачи данных, но также в маршрутизаторах, принтерах, планшетах, мобильных телефонах, телевизионных приставках, аудиоаппаратуре, медиаплеерах и т. Д. Она имеет длинный список функций, который включает поддержку для IPv6 и socks5, пользовательские результаты вывода после завершения, без ограничения длины URL, асинхронное разрешение имен.

4. Wget

Wget – это утилита командной строки с открытым исходным кодом для извлечения контента с веб-серверов через прокси-серверы HTTP, а также протоколы HTTP, HTTPS и FTP. Его функция – рекурсивная загрузка, которая подразумевает, что он следует по ссылкам на HTML-страницах и создает локальные версии удаленных веб-сайтов.

Wget может похвастаться несколькими функциями, включая способность превосходно функционировать даже при медленном или нестабильном сетевом подключении, поддержку прокси-серверов HTTP и файлов cookie, возобновление прерванных загрузок с использованием API REST и RANGE, файлы сообщений на основе NLS для разных языков и т. Д.

Wget – скачать файлы в определенный каталог

5. Aria2

Aria2 – это легкая утилита загрузки с открытым исходным кодом для командной строки с поддержкой HTTP и HTTPS, FTP и SFTP, Metalink и BitTorrent. Его функции включают в себя автоматическую проверку для таких файлов, как BitTorrent , параллельные загрузки файлов с HTTP (S)/(S) FTP и BitTorrent одновременно, поддержку Ntrc, кэширование диска для снижения активности диска, поддержку IPv6 с Happy Eyeballs и т. Д.

Есть ли какие-нибудь классные HTTP-клиенты командной строки, которые не перечислены выше? Не стесняйтесь добавлять свои варианты в комментарии.

Источник

s_client(1) — Linux man page

s_client — SSL/TLS client program

Synopsis

openssl s_client [-connect host:port] [-verify depth] [-cert filename] [-certform DER|PEM] [-key filename] [-keyform DER|PEM] [-pass arg] [-CApath directory] [-CAfile filename] [-reconnect] [-pause] [-showcerts] [-debug] [-msg] [-nbio_test] [-state] [-nbio] [-crlf] [-ign_eof] [-quiet] [-ssl2] [-ssl3] [-tls1] [-no_ssl2] [-no_ssl3] [-no_tls1] [-bugs] [-cipher cipherlist] [-starttls protocol] [-engine id] [-tlsextdebug] [-no_ticket] [-sess_out filename] [-sess_in filename] [-rand file(s)]

Description

The s_client command implements a generic SSL/TLS client which connects to a remote host using SSL/TLS . It is a very useful diagnostic tool for SSL servers.

Options

-connect host:port This specifies the host and optional port to connect to. If not specified then an attempt is made to connect to the local host on port 4433. -cert certname The certificate to use, if one is requested by the server. The default is not to use a certificate. -certform format The certificate format to use: DER or PEM . PEM is the default. -key keyfile The private key to use. If not specified then the certificate file will be used. -keyform format The private format to use: DER or PEM . PEM is the default. -pass arg the private key password source. For more information about the format of arg see the PASS PHRASE ARGUMENTS section in openssl(1). -verify depth The verify depth to use. This specifies the maximum length of the server certificate chain and turns on server certificate verification. Currently the verify operation continues after errors so all the problems with a certificate chain can be seen. As a side effect the connection will never fail due to a server certificate verify failure. -CApath directory The directory to use for server certificate verification. This directory must be in «hash format», see verify for more information. These are also used when building the client certificate chain. -CAfile file A file containing trusted certificates to use during server authentication and to use when attempting to build the client certificate chain. -purpose, -ignore_critical, -issuer_checks, -crl_check, -crl_check_all, -policy_check, -extended_crl, -x509_strict, -policy -check_ss_sig Set various certificate chain valiadition option. See the verify manual page for details. -reconnect reconnects to the same server 5 times using the same session ID , this can be used as a test that session caching is working. -pause pauses 1 second between each read and write call. -showcerts display the whole server certificate chain: normally only the server certificate itself is displayed. -prexit print session information when the program exits. This will always attempt to print out information even if the connection fails. Normally information will only be printed out once if the connection succeeds. This option is useful because the cipher in use may be renegotiated or the connection may fail because a client certificate is required or is requested only after an attempt is made to access a certain URL . Note: the output produced by this option is not always accurate because a connection might never have been established. -state prints out the SSL session states. -debug print extensive debugging information including a hex dump of all traffic. -msg show all protocol messages with hex dump. -nbio_test tests non-blocking I/O -nbio turns on non-blocking I/O -crlf this option translated a line feed from the terminal into CR+LF as required by some servers. -ign_eof inhibit shutting down the connection when end of file is reached in the input. -quiet inhibit printing of session and certificate information. This implicitly turns on -ign_eof as well. -psk_identity identity Use the PSK identity identity when using a PSK cipher suite. -psk key Use the PSK key key when using a PSK cipher suite. The key is given as a hexadecimal number without leading 0x, for example -psk 1a2b3c4d. -ssl2, -ssl3, -tls1, -no_ssl2, -no_ssl3, -no_tls1 these options disable the use of certain SSL or TLS protocols. By default the initial handshake uses a method which should be compatible with all servers and permit them to use SSL v3, SSL v2 or TLS as appropriate.

Unfortunately there are a lot of ancient and broken servers in use which cannot handle this technique and will fail to connect. Some servers only work if TLS is turned off with the -no_tls option others will only support SSL v2 and may need the -ssl2 option. -bugs there are several known bug in SSL and TLS implementations. Adding this option enables various workarounds. -cipher cipherlist this allows the cipher list sent by the client to be modified. Although the server determines which cipher suite is used it should take the first supported cipher in the list sent by the client. See the ciphers command for more information. -starttls protocol send the protocol-specific message(s) to switch to TLS for communication. protocol is a keyword for the intended protocol. Currently, the only supported keywords are «smtp», «pop3», «imap», and «ftp». -tlsextdebug print out a hex dump of any TLS extensions received from the server. -no_ticket disable RFC4507bis session ticket support. -sess_out filename output SSL session to filename -sess_in sess.pem load SSL session from filename. The client will attempt to resume a connection from this session. -engine id specifying an engine (by its unique id string) will cause s_client to attempt to obtain a functional reference to the specified engine, thus initialising it if needed. The engine will then be set as the default for all available algorithms. -rand file(s) a file or files containing random data used to seed the random number generator, or an EGD socket (see rand_egd(3)). Multiple files can be specified separated by a OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others.

Connected Commands

If a connection is established with an SSL server then any data received from the server is displayed and any key presses will be sent to the server. When used interactively (which means neither -quiet nor -ign_eof have been given), the session will be renegotiated if the line begins with an R, and if the line begins with a Q or if end of file is reached, the connection will be closed down.

Notes

s_client can be used to debug SSL servers. To connect to an SSL HTTP server the command: would typically be used (https uses port 443). If the connection succeeds then an HTTP command can be given such as » GET /» to retrieve a web page.

If the handshake fails then there are several possible causes, if it is nothing obvious like no client certificate then the -bugs, -ssl2, -ssl3, -tls1, -no_ssl2, -no_ssl3, -no_tls1 options can be tried in case it is a buggy server. In particular you should play with these options before submitting a bug report to an OpenSSL mailing list.

A frequent problem when attempting to get client certificates working is that a web client complains it has no certificates or gives an empty list to choose from. This is normally because the server is not sending the clients certificate authority in its «acceptable CA list» when it requests a certificate. By using s_client the CA list can be viewed and checked. However some servers only request client authentication after a specific URL is requested. To obtain the list in this case it is necessary to use the -prexit option and send an HTTP request for an appropriate page.

If a certificate is specified on the command line using the -cert option it will not be used unless the server specifically requests a client certificate. Therefor merely including a client certificate on the command line is no guarantee that the certificate works.

If there are problems verifying a server certificate then the -showcerts option can be used to show the whole chain.

Since the SSLv23 client hello cannot include compression methods or extensions these will only be supported if its use is disabled, for example by using the -no_sslv2 option.

Because this program has a lot of options and also because some of the techniques used are rather old, the C source of s_client is rather hard to read and not a model of how things should be done. A typical SSL client program would be much simpler.

The -verify option should really exit if the server verification fails.

The -prexit option is a bit of a hack. We should really report information whenever a session is renegotiated.

Источник