{"id":35486,"date":"2019-10-31T22:04:36","date_gmt":"2019-10-31T19:04:36","guid":{"rendered":"https:\/\/prohoster.info\/blog\/vypusk-http-tcp-balansirovshhika-haproxy-2-0\/"},"modified":"2019-10-31T22:04:36","modified_gmt":"2019-10-31T19:04:36","slug":"vypusk-http-tcp-balansirovshhika-haproxy-2-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-http-tcp-balansirovshhika-haproxy-2-0","title":{"rendered":"Lan\u00e7amento do balanceador de carga HTTP\/TCP HAProxy 2.0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><noindex><a rel=\"nofollow\" href=\"https:\/\/www.haproxy.com\/blog\/haproxy-2-0-and-beyond\/\">Publicado<\/a><\/noindex> lan\u00e7amento do balanceador de carga <noindex><a rel=\"nofollow\" href=\"http:\/\/www.haproxy.org\">com o encaminhamento de solicita\u00e7\u00f5es atrav\u00e9s do TCP sobre IPv4 e IPv6 ou sem encaminhamento de conex\u00f5es (para envio de solicita\u00e7\u00f5es heartbeat de verifica\u00e7\u00e3o, confirmando que est\u00e1 em opera\u00e7\u00e3o normal).<\/a><\/noindex>, permitindo distribuir o tr\u00e1fego HTTP e solicita\u00e7\u00f5es TCP arbitr\u00e1rias entre um grupo de servidores, considerando diversos fatores (por exemplo, verifica a disponibilidade dos servidores, avalia o n\u00edvel de carga, possui mecanismos de defesa contra DDoS) e realiza uma filtragem inicial de dados (como analisar cabe\u00e7alhos HTTP, filtrar a passagem de par\u00e2metros de solicita\u00e7\u00e3o inv\u00e1lidos, bloquear inje\u00e7\u00e3o SQL e XSS, conectar agentes de processamento de conte\u00fado). O HAProxy tamb\u00e9m pode <noindex><a rel=\"nofollow\" href=\"https:\/\/www.haproxy.com\/solutions\/microservices\/\">ser usados<\/a><\/noindex> para coordenar a intera\u00e7\u00e3o de componentes em sistemas baseados na arquitetura de microservi\u00e7os. O c\u00f3digo do projeto \u00e9 escrito em C e <noindex><a rel=\"nofollow\" href=\"http:\/\/git.haproxy.org\/\">\u00e9 disponibilizado<\/a><\/noindex> sob licen\u00e7a GPLv2. O projeto \u00e9 utilizado em muitos sites grandes, incluindo Airbnb, Alibaba, GitHub, Imgur, Instagram, Reddit, StackOverflow, Tumblr, Twitter e Vimeo.<\/p>\n<p>Principais caracter\u00edsticas do lan\u00e7amento:<\/p>\n<ul>\n<li class=\"l\"> Um novo API <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/haproxytech\/dataplaneapi\">Data Plan<\/a><\/noindex>, que permite gerenciar as configura\u00e7\u00f5es do HAProxy em tempo real atrav\u00e9s da REST Web API. \u00c9 poss\u00edvel adicionar e remover dinamicamente backends e servidores, criar ACLs, alterar o roteamento de solicita\u00e7\u00f5es, modificar associa\u00e7\u00f5es de manipuladores a IPs;\n<li class=\"l\"> Foi adicionada a diretiva nbthread, que permite configurar o n\u00famero de threads usadas no HAProxy para otimizar o desempenho em CPUs multin\u00facleo. Por padr\u00e3o, o n\u00famero de threads de trabalho \u00e9 selecionado com base nos n\u00facleos de CPU dispon\u00edveis no ambiente atual, e em ambientes de nuvem, um \u00fanico thread \u00e9 configurado por padr\u00e3o. Para definir limites r\u00edgidos, foram adicionadas op\u00e7\u00f5es de configura\u00e7\u00e3o MAX_THREADS e MAX_PROCS, que limitam o m\u00e1ximo de threads e processos;\n<li class=\"l\"> Simplificou o uso da diretiva bind para vincular manipuladores a endere\u00e7os de rede. Agora, ao configurar, n\u00e3o \u00e9 necess\u00e1rio definir par\u00e2metros do processo \u2014 por padr\u00e3o, as conex\u00f5es ser\u00e3o distribu\u00eddas entre os threads de acordo com o n\u00famero de conex\u00f5es ativas.\n<li class=\"l\"> A configura\u00e7\u00e3o de logs foi simplificada ao ser executada em cont\u00eaineres isolados \u2014 o log agora pode ser direcionado para stdout e stderr, bem como para qualquer descritor de arquivo existente (por exemplo, \"log fd@1 local0\");\n<li class=\"l\"> O suporte ao HTX (Representa\u00e7\u00e3o HTTP Nativa) est\u00e1 habilitado por padr\u00e3o, permitindo o balanceamento ao utilizar funcionalidades avan\u00e7adas como HTTP\/2 de ponta a ponta, Repeti\u00e7\u00f5es na Camada 7 e gRPC. O HTX n\u00e3o substitui os cabe\u00e7alhos in-loco, mas reduz a opera\u00e7\u00e3o de modifica\u00e7\u00e3o a remover e adicionar um novo cabe\u00e7alho ao final da lista, permitindo manipular quaisquer variantes avan\u00e7adas do protocolo HTTP, mantendo a sem\u00e2ntica original dos cabe\u00e7alhos e alcan\u00e7ando melhor desempenho na transi\u00e7\u00e3o de HTTP\/2 para HTTP\/1.1 e vice-versa;\n<li class=\"l\"> Adicionada a suporte oficial ao modo de Ponta a Ponta HTTP\/2 (processamento em todas as etapas em HTTP\/2, incluindo chamadas ao backend, e n\u00e3o apenas a intera\u00e7\u00e3o do proxy com o cliente);\n<li class=\"l\"> Implementado suporte completo para proxy bidirecional do protocolo gRPC com capacidade de an\u00e1lise de fluxos gRPC, destacando mensagens individuais, refletindo o tr\u00e1fego gRPC no log e filtrando mensagens usando ACL. O gRPC permite a opera\u00e7\u00e3o de microservi\u00e7os em v\u00e1rias linguagens de programa\u00e7\u00e3o que se comunicam entre si atrav\u00e9s de uma API universal. A intera\u00e7\u00e3o em rede no gRPC \u00e9 feita sobre o protocolo HTTP\/2 e baseia-se no uso de Protocol Buffers para a serializa\u00e7\u00e3o de dados.\n<li class=\"l\"> Adicionada a suporte para o modo \"Layer 7 Retries\", que permite reenviar requisi\u00e7\u00f5es HTTP em caso de falhas program\u00e1ticas n\u00e3o relacionadas a problemas de conex\u00e3o de rede (por exemplo, na aus\u00eancia de resposta ou resposta vazia em uma requisi\u00e7\u00e3o POST). Para desativar o modo, o flag \"disable-l7-retry\" foi adicionado \u00e0 op\u00e7\u00e3o \"http-request\", e para ajustes finos, as se\u00e7\u00f5es defaults, listen e backend agora oferecem a op\u00e7\u00e3o \"retry-on\". Os seguintes sinais est\u00e3o dispon\u00edveis para reenvio: all-retryable-errors, none, conn-failure, empty-response, junk-response, response-timeout, 0rtt-rejected, al\u00e9m de vincula\u00e7\u00e3o a c\u00f3digos de status retornados (404 e assim por diante);\n<li class=\"l\"> Implementado um novo gerenciador de processos (Process Manager), permitindo a configura\u00e7\u00e3o da chamada de arquivos execut\u00e1veis externos com manipuladores para o HAProxy.<br \/>\nPor exemplo, este manipulador externo foi implementado como API Data Plan (\/usr\/sbin\/dataplaneapi), al\u00e9m de v\u00e1rios mecanismos de processamento Offload;<\/p>\n<li class=\"l\"> Adicionados bindings para .NET Core, Go, Lua e Python para o desenvolvimento de extens\u00f5es SPOE (Stream Processing Offload Engine) e SPOP (Stream Processing Offload Protocol). Anteriormente, apenas o desenvolvimento de extens\u00f5es em C era suportado;\n<li class=\"l\"> Adicionado o manipulador externo spoa-mirror ( \/usr\/sbin\/spoa-mirror ) para espelhar solicita\u00e7\u00f5es em um servidor separado (por exemplo, para copiar parte do tr\u00e1fego de trabalho para testar um ambiente experimental sob carga real);\n<li class=\"l\"> Apresentado  <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/haproxytech\/kubernetes-ingress\/\">Controlador de Ingress HAProxy Kubernetes<\/a><\/noindex> para garantir a integra\u00e7\u00e3o com a plataforma Kubernetes;\n<li class=\"l\"> Adicionada suporte interno para exportar estat\u00edsticas para o sistema de monitoramento <noindex><a rel=\"nofollow\" href=\"https:\/\/prometheus.io\/\">Prometheus<\/a><\/noindex>;\n<li class=\"l\"> O protocolo Peers Protocol foi expandido, usado para troca de informa\u00e7\u00f5es com outros n\u00f3s usando HAProxy. Inclui suporte para Heartbeat e transmiss\u00e3o de dados criptografada;\n<li class=\"l\"> Adicionado um par\u00e2metro \"sample\" \u00e0 diretiva \"log\", que permite registrar apenas uma parte das requisi\u00e7\u00f5es, por exemplo, 1 em 10, para forma\u00e7\u00e3o de amostras anal\u00edticas;\n<li class=\"l\"> Adicionado um modo de perfilamento autom\u00e1tico (diretiva profiling.tasks, que pode aceitar os valores auto, on e off). O perfilamento autom\u00e1tico \u00e9 ativado quando a lat\u00eancia m\u00e9dia ultrapassa a marca de 1000 ms. Para visualizar os dados de perfilamento na API em tempo de execu\u00e7\u00e3o, foi adicionada o comando \"show profiling\" ou \u00e9 poss\u00edvel redefinir as estat\u00edsticas no log;\n<li class=\"l\"> Adicionada suporte para requisi\u00e7\u00f5es a servidores backend usando o protocolo SOCKS4;\n<li class=\"l\"> Suporte adicionado para um mecanismo de abertura r\u00e1pida de conex\u00f5es TCP (TFO \u2014 TCP Fast Open, RFC 7413) de ponta a ponta, abrangendo o backend, que permite reduzir o n\u00famero de passos na configura\u00e7\u00e3o da conex\u00e3o ao combinar em um \u00fanico pedido a primeira e a segunda etapas do cl\u00e1ssico processo de 3 etapas de negocia\u00e7\u00e3o de conex\u00e3o e possibilita o envio de dados na fase inicial da configura\u00e7\u00e3o da conex\u00e3o;\n<li class=\"l\"> Novas a\u00e7\u00f5es foram adicionadas:\n<ul>\n<li class=\"l\"> \"http-request replace-uri\" para substitui\u00e7\u00e3o de URL usando express\u00e3o regular;\n<li class=\"l\"> \"tcp-request content do-resolve\" e \"http-request do-resolve\" para resolu\u00e7\u00e3o de nome de host;\n<li class=\"l\">  \"tcp-request content set-dst\" e \"tcp-request content set-dst-port\" para substitui\u00e7\u00e3o do IP de destino e da porta.\n<\/ul>\n<li class=\"l\"> Novos m\u00f3dulos de convers\u00e3o adicionados:\n<ul>\n<li class=\"l\"> aes_gcm_dev para descriptografar fluxos usando algoritmos AES128-GCM, AES192-GCM e AES256-GCM;\n<li class=\"l\"> protobuf para extrair campos de mensagens Protocol Buffers;\n<li class=\"l\"> ungrpc para extrair campos de mensagens gRPC.\n<\/ul>\n<p><noindex><a rel=\"nofollow\" name=\"link\"><\/a><\/noindex><\/p>\n<p>Fonte: <a \ncontent=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=50904\">opennet.ru<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d \u0440\u0435\u043b\u0438\u0437 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 HAProxy 2.0, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0435\u0433\u043e \u0440\u0430\u0441\u043f\u0440\u0435\u0434\u0435\u043b\u044f\u0442\u044c HTTP-\u0442\u0440\u0430\u0444\u0438\u043a \u0438 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u043b\u044c\u043d\u044b\u0435 TCP-\u0437\u0430\u043f\u0440\u043e\u0441\u044b \u043c\u0435\u0436\u0434\u0443 \u0433\u0440\u0443\u043f\u043f\u043e\u0439 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432, \u0443\u0447\u0438\u0442\u044b\u0432\u0430\u044f \u043c\u043d\u043e\u0436\u0435\u0441\u0442\u0432\u043e \u0444\u0430\u043a\u0442\u043e\u0440\u043e\u0432 (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043f\u0440\u043e\u0432\u0435\u0440\u044f\u0435\u0442 \u0434\u043e\u0441\u0442\u0443\u043f\u043d\u043e\u0441\u0442\u044c \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432, \u043e\u0446\u0435\u043d\u0438\u0432\u0430\u0435\u0442 \u0443\u0440\u043e\u0432\u0435\u043d\u044c \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438, \u0438\u043c\u0435\u0435\u0442 \u0441\u0440\u0435\u0434\u0441\u0442\u0432\u0430 \u043f\u0440\u043e\u0442\u0438\u0432\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u044f DDoS) \u0438 \u043f\u0440\u043e\u0432\u043e\u0434\u0438\u0442 \u043f\u0435\u0440\u0432\u0438\u0447\u043d\u0443\u044e \u0444\u0438\u043b\u044c\u0442\u0440\u0430\u0446\u0438\u044e \u0434\u0430\u043d\u043d\u044b\u0445 (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, \u043c\u043e\u0436\u043d\u043e \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c HTTP-\u0437\u0430\u0433\u043e\u043b\u043e\u0432\u043a\u0438, \u043e\u0442\u0444\u0438\u043b\u044c\u0442\u0440\u043e\u0432\u044b\u0432\u0430\u0442\u044c \u043f\u0435\u0440\u0435\u0434\u0430\u0447\u0443 \u043d\u0435\u043a\u043e\u0440\u0440\u0435\u043a\u0442\u043d\u044b\u0445 \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u043e\u0432 \u0437\u0430\u043f\u0440\u043e\u0441\u0430, \u0431\u043b\u043e\u043a\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u043f\u043e\u0434\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0443 SQL \u0438 XSS, \u043f\u043e\u0434\u043a\u043b\u044e\u0447\u0430\u0442\u044c \u0430\u0433\u0435\u043d\u0442\u044b \u043e\u0431\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043a\u043e\u043d\u0442\u0435\u043d\u0442\u0430). HAProxy \u0442\u0430\u043a\u0436\u0435 \u043c\u043e\u0436\u0435\u0442 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-35486","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d \u0440\u0435\u043b\u0438\u0437 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 HAProxy.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-http-tcp-balansirovshhika-haproxy-2-0\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"pt_PT\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0412\u044b\u043f\u0443\u0441\u043a HTTP\/TCP-\u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 HAProxy 2.0 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d \u0440\u0435\u043b\u0438\u0437 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 HAProxy.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-http-tcp-balansirovshhika-haproxy-2-0\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T19:04:36+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T19:04:36+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Lan\u00e7amento do balanceador HAProxy HTTP\/TCP 2.0 | ProHoster","description":"Publicada a vers\u00e3o do balanceador de carga HAProxy.","canonical_url":"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-http-tcp-balansirovshhika-haproxy-2-0","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"pt_PT","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0412\u044b\u043f\u0443\u0441\u043a HTTP\/TCP-\u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 HAProxy 2.0 | ProHoster","og:description":"\u041e\u043f\u0443\u0431\u043b\u0438\u043a\u043e\u0432\u0430\u043d \u0440\u0435\u043b\u0438\u0437 \u0431\u0430\u043b\u0430\u043d\u0441\u0438\u0440\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438 HAProxy.","og:url":"https:\/\/prohoster.info\/pt\/blog\/news\/vypusk-http-tcp-balansirovshhika-haproxy-2-0","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T19:04:36+00:00","article:modified_time":"2019-10-31T19:04:36+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"35486","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 23:28:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:01:26","updated":"2026-01-21 23:28:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/35486","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/comments?post=35486"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/posts\/35486\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/media?parent=35486"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/categories?post=35486"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/pt\/wp-json\/wp\/v2\/tags?post=35486"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}