Nexpose 8.38.0 for Linux & Windows - 漏洞扫描 - sysin | 软件与技术分享 | SYStem INside Nexpose 8.38.0 for Linux & Windows - 漏洞扫描 - sysin | 软件与技术分享 | SYStem INside

Nexpose 8.40.0 for Linux & Windows - 漏洞扫描 请访问原文链接： Nexpose 8.40.0 for Linux & Windows - 漏洞扫描 查看最新版。

#HTTP #Linux #Security #Windows #Rapid7

Origin | Interest | Match

Pausing traffic and retrying in Caddy #http #pattern #reading-list

🔗 Pausing traffic and retrying in Caddy

#http #pattern #reading-list

Call REST APIs from Xojo with URLConnection. Send GET/POST async/sync, set headers, handle auth, download files. HTTPS built‑in.

👉 documentation.xojo.com/api/networking/urlconnec...
#Xojo #HTTP #API

The instance is up. or is it? Health checking in client-side vs server-side load balancing #http #reading-list

🔗 The instance is up. or is it? Health checking in client-side vs server-side load balancing

#http #reading-list

Request validation in Phoenix: the Laravel FormRequest approach #database #ElixirLang #ElixirPhoenix #http #laravel #phoenix #php

🐥 Request validation in Phoenix: the Laravel FormRequest approach

#database #ElixirLang #ElixirPhoenix #http #laravel #phoenix #php

GitHub - Huachao/vscode-restclient: REST Client Extension for Visual Studio Code REST Client Extension for Visual Studio Code. Contribute to Huachao/vscode-restclient development by creating an account on GitHub.

Will someone take over maintaining github.com/Huachao/v... ?
Seems very dead right now. :/

#vscode #extension #rest #http

Прокидання потоку Icecast/HTTP через Tor з socat Ситуація така, що поточний сервер не має Інтернет-інтерфейсу, зате має Yggdrasil, а той в свою чергу - мости Tor. Оскільки Tor працює на проксі SOCKS5, певна річ, Icecast того проксування з коробки не вміє. В мене були спроби пустити потік через: pr...

Прокидання потоку Icecast/HTTP через Tor з socat

#icecast #tor #socat #proxy #http #socks

UGraphQuery - Tools for GraphQL UGraphQuery is a powerful Unity plugin designed to seamlessly integrate GraphQL capabilities into your Unity projects.

#Unitynetworking #Lightweight #Desktop #Tools #Highperformance #Game #Websocket #Graphqlforunity #Mobile #Easy #Web #Webgl #Networking #Http

SSH is the new/old Web.

#ssh #http #https #web #www

Understanding Agent, GenServer, Task, and ETS in Elixir #database #ElixirLang #http #pattern

🐥 Understanding Agent, GenServer, Task, and ETS in Elixir

#database #ElixirLang #http #pattern

Just a moment...

Explore implementing #HTTP retries with the Factory Pattern for more reliable network requests! Discover best practices on creating robust and maintainable retry logic in .NET. #DotNetInnovations

Original post on front-end.social

🦖 Content-Digest header 🦖

developer.mozilla.org/en-US/docs/Web/HTTP/Refe...

The HTTP Content-Digest request and response header provides a digest calculated using a hashing algorithm applied to the message content. A recipient can use the Content-Digest to […]

Metasploit Framework 6.4.123 (macOS, Linux, Windows) - 开源渗透测试框架 - sysin | 软件与技术分享 | SYStem INside Metasploit Framework 6.4.123 (macOS, Linux, Windows) - 开源渗透测试框架 - sysin | 软件与技术分享 | SYStem INside

Metasploit Framework 6.4.123 (macOS, Linux, Windows) - 开源渗透测试框架 请访问原文链接： Metasploit Framework 6.4.123 (macOS, Linux, Windows) - 开源渗透测试框架 查看最新...

#HTTP #Linux #macOS #Security #Windows #Rapid7

Origin | Interest | Match

Python library “Requests” needs you to test type hints Requests is a popular HTTP client library available on the Python Package Index (PyPI). Sitting in the top 10 packages by downloads on PyPI, this library is used by many, many projects. This librar...

The popular #Python library “Requests” needs your help! @nateprewitt@fosstodon.org plans to add type hints to the API and is requesting feedback:

sethmlarson.dev/python-libra...

#typing #http #typehints

Original post on front-end.social

🦖 422 Unprocessable Content 🦖

developer.mozilla.org/en-US/docs/Web/HTTP/Refe...

The HTTP 422 Unprocessable Content client error response status code indicates that the server understood the content type of the request content, and the syntax of the request content was […]

curl

cURL (curl.se) is one of my favorite tools when working with REST APIs. The use of this tool is found in almost all scripts.
With it, you can test your HTTP handlers and even write example requests and responses in the service documentation.

#curl #Web #HTTP #REST #API #HTTPie #xh #POST #GET

comiCSS comiCSS Games: games about CSS. Coded in CSS (mostly).

#Development #Fun
Front-end Crossword · The crossword puzzle for front-end developers ilo.im/16baxk by Álvaro Montoro

_____
#HTML #CSS #JavaScript #Forms #Accessibility #ARIA #Images #HTTP #WebDev #Frontend

Nessus 10.11 Auto Installer for Ubuntu 24.04 - Nessus 自动化安装程序 (updated Feb 2026) - sysin | 软件与技术分享 | SYStem INside Nessus 10.11 Auto Installer for Ubuntu 24.04 - Nessus 自动化安装程序 (updated Feb 2026) - sysin | 软件与技术分享 | SYStem INside

Nessus 10.11 Auto Installer for Ubuntu 24.04 - Nessus 自动化安装程序 (updated Mar 2026) 请访问原文链接： Nessus 10.11 Auto Installer for Ubuntu 24.04 - Nessus 自动化安装程序 (...

#HTTP #Linux #Security

Origin | Interest | Match

Nessus 10.11 Auto Installer for RHEL 9 | RHEL 10 - Nessus 自动化安装程序 (updated Mar 2026) - sysin | 软件与技术分享 | SYStem INside Nessus 10.11 Auto Installer for RHEL 9 | RHEL 10 - Nessus 自动化安装程序 (updated Mar 2026) - sysin | 软件与技术分享 | SYStem INside

Nessus 10.11 Auto Installer for RHEL 9 | RHEL 10 - Nessus 自动化安装程序 (updated Mar 2026) 请访问原文链接： Nessus 10.11 Auto Installer for RHEL 9 | RHEL 10 - Nessus 自动化安装...

#HTTP #Linux #Security

Origin | Interest | Match

Wednesday Links - Edition 2026-03-11 Java 26 for DevOps (2 min)☕ https://inside.java/2026/03/02/jdk-26-rn-ops/ HTTP Client Updates in...

Wednesday Links - Edition 2026-03-11
dev.to/0xkkocel/wed...
#java #jvm #http #springboot #dpop #quarkus #postgres #claude

Original post on mstdn.social

System Administration: Week 7: DNS & HTTP

We're moving from the DNS on to HTTP. Sorry, no videos for this subtopic, but here are the slides from our last class. We discuss how to get your domain registered and then move on to summarize briefly HTTP the protocol and look at what CDNs do […]

Original post on front-end.social

🦖 Sec-WebSocket-Protocol header
✅ Widely available (from Jul 2015)

developer.mozilla.org/en-US/docs/Web/HTTP/Refe...

The HTTP Sec-WebSocket-Protocol request and response header is used in the WebSocket opening handshake to negotiate a sub-protocol to […]

Cross-site request forgery #html #http #reading-list

🔗 Cross-site request forgery

#html #http #reading-list

Metasploit Framework 6.4.115 (macOS, Linux, Windows) - 开源渗透测试框架 - sysin | 软件与技术分享 | SYStem INside Metasploit Framework 6.4.115 (macOS, Linux, Windows) - 开源渗透测试框架 - sysin | 软件与技术分享 | SYStem INside

Metasploit Framework 6.4.120 (macOS, Linux, Windows) - 开源渗透测试框架 请访问原文链接： Metasploit Framework 6.4.120 (macOS, Linux, Windows) - 开源渗透测试框架 查看最新...

#HTTP #Linux #macOS #Security #Windows #Rapid7

Origin | Interest | Match

Metasploit Pro 5.0.0 (Linux, Windows) 发布 - 专业渗透测试框架 - sysin | 软件与技术分享 | SYStem INside Metasploit Pro 5.0.0 (Linux, Windows) 发布 - 专业渗透测试框架 - sysin | 软件与技术分享 | SYStem INside

Metasploit Pro 5.0.0 (Linux, Windows) 发布 - 专业渗透测试框架 请访问原文链接： Metasploit Pro 5.0.0 (Linux, Windows) 发布 - 专业渗透测试框架 查看最新版。

#HTTP #Linux #Security #Windows #Rapid7

Origin | Interest | Match

CSRF Protection without Tokens or Hidden Form Fields A couple of months ago, I received a request from a random Internet user to add CSRF protection to my little web framework Microdot, and I thought it was a fantastic idea.When I set off to do this…

Protection anti CSRF à l'aide du header `Sec-Fetch-Site`.

🔗 blog.miguelgrinberg.com/post/csrf-protection-wit...

#csrf #HTTP #sécurité

Original post on danq.me

[Repost: I Am Experimenting with Blocking HTTP1.1]

Andrew Stephens has added Caddy configuration to prohibit HTTP/1 clients from accessing most of the pages of his website. I decided to probe it and see how that works.
Read more […]

Why I dislike .well-known There is a growing trend for new protocols to express themselves in the form of a well-known URI. It’s seen as an easy place to stash something where other interoperable software might want to probe for protocol support, as an improvement to the old ad-hoc behavior of things like `robots.txt` and `favicon.ico` and the like. I am not personally a fan of it, for a few reasons. The big one is that it means that all discovery for all uses of a protocol must be uniform across all areas on a single domain. For example, if you have URLs like `https://example.com/~alice/` and `https://example.com/~bob/` and both of them want to support the `foo` protocol, then `https://example.com/.well-known/foo` needs to have some means of distinguishing the two. And the way of doing that can be tricky. Do you have something like `https://example.com/.well-known/foo?resource=/~alice/`? How do you deal with path normalization (e.g. `/~alice` vs `~alice/` vs. `~alice/homepage.html`)? Do you have to consider things like cross-domain attacks? What if multiple users on a tilde site want to support different sets of protocols, or use different implementations? Putting things into the query string (the most typical approach for this) also means that you’re going to have to have some sort of dynamic mapping or request routing, which means this can’t work with purely static hosting. It also means that you might have to probe for this protocol support across every single URL being accessed on a domain. Another concern is that every protocol you want to support requires a separate HTTP request, and these things can add up pretty quickly. For example, whenever I post an article to my website and it goes out on my Mastodon feed, I get many dozens of Mastodon instances each probing an absolute litany of related URLs trying to determine whether this is a Mastodon instance or similar, and sometimes this ends up even overwhelming my server. Even without that, I’m getting a constant flood of requests for things like `/.well-known/traffic-advice` and `/.well-known/wp-login.php` and the like. A much better approach, in my opinion, is to have the discovery baked into the resource itself. In HTML you can use the `<link>` tag (e.g. `<link rel="foo" href="/~alice/foo-support.xml">`)1 and in HTTP in general you can use the `Link:` header (e.g. `Link: <https://example.com/%7Ealice/foo-support.xml>; rel=foo`). A single HTTP request can tell a client about _all_ possibly-supported protocols, all at once, and it can be baked in statically and thus supports static hosting. It also means there is no special case for handling multiple resources across a single domain, and if two pages have the exact same link target it can also be inferred that they are the same as far as that protocol is concerned. One concern that comes up is that of page bloat, when every page needs to include a bunch of `<link>` tags to express a growing list of supported protocols. This is, to me, a non-issue; for starters, you’re only declaring the protocols that you actually support, and it’s a single point of reference for all clients to discover all of the supported protocols. But also, the amount of bandwidth added to a page for even a few dozen protocols is miniscule compared to the amount of bandwidth taken by other accepted optimizations, such as inline CSS and `data:` blobs for images, as well as the bandwidth taken up by the incessant `.well-known` probes that are taking place at this point. A suite of related protocols could also be offered as a forwarding URL, such as IndieAuth’s current practice of bundling it all together into indieauth-metadata. This does require an extra HTTP request, but it only has to happen once, as that URL is extremely cacheable. The IndieWeb wiki has more to say about the growing usage of `.well-known` and why it’s considered an antipattern. As an aside, I am also not a fan of Webfinger, because not only does it require `.well-known` to work, but it attempts to flatten a namespace in ways that are difficult to deal with. On this website, you can easily get the update feed for any given section by discovering its `rel="alternate"` URLs, but there is no such mechanism in Webfinger; you can follow _the site as a whole_ as `@beesbuzz.biz@beesbuzz.biz` (thanks to Bridgy Fed) but you can’t follow just the `/code/` section, for example. There are some hacks such as making `@code@beesbuzz.biz`, `@comics@beesbuzz.biz` and so on, but then what about nested subdirectories (e.g. `/food/coffee/`)? Why not just use the URL itself as the specifier? With `<link>`-based discovery, you already can, and there’s nothing special about it. So, anyway: When designing a new protocol, please consider _not_ using `.well-known` URLs for discovery purposes. Let the URL itself provide its own information. 1. In some cases, such as content feeds, it can be a bit unclear as to whether you should use an existing `rel` (such as `alternate`) with an appropriate `type` to disambiguate, or if you should invent a new `rel`, but that’s a much smaller problem than those caused by `.well-known` creep. ↩ The general rule of thumb seems to be that if you’re designing an active interface-type protocol (e.g. something with a specific RESTful API), you should invent a new `rel`, and if you’re designing a feed format or other such alternate representation of a page’s content you should use `rel="alternate"`, although that does require some interpolation of the MDN Link Types document and the general common practices across the IndieWeb and Microformats communities.

busybee: Code: Why I dislike .well-known beesbuzz.biz/code/6987-Why-I-dislike-... #Internet #Code #HTTP #Web

Beyond Static Resources: Delta Compression for Dynamic HTML Compression Dictionary Transport (RFC 9842), authored by Patrick Meenan and Yoav Weiss, lets browsers...

Beyond Static Resources: Delta Compression for Dynamic HTML Compression Dictionary Transport ( RFC 9842 ), authored by Patrick Meenan and Yoav Weiss, lets browsers use previously seen content as co...

#webperf #http #compression

Origin | Interest | Match

Beyond Static Resources: Delta Compression for Dynamic HTML Compression Dictionary Transport (RFC 9842), authored by Patrick Meenan and Yoav Weiss, lets browsers...

Beyond Static Resources: Delta Compression for Dynamic HTML Compression Dictionary Transport ( RFC 9842 ), authored by Patrick Meenan and Yoav Weiss, lets browsers use previously seen content as co...

#webperf #http #compression

Origin | Interest | Match