Recently at work, at SNCF Connect & Tech, we needed to expose some static documents as HTTP endpoints: a GET /version that would provide some information about the application version as JSON, and a GET /openapi/yaml that would return the OpenAPI 3 specification of our HTTP API as YAML.

We …

Linkback protocols are an old breed. They were born in a time where MySpace, Wikipedia & WordPress had just been born, and Friendster was more popular than this new website called Facebook.

The latest linkback protocol, Webmention, is relatively recent though, as it became a W3C …

Covering :

• Persistent Connections
• Parallelism
• Asynchronicity
• Performances:

  Time needed for `serialized' called: 12.12s
  Time needed for `Session' called: 11.22s
  Time needed for `FuturesSession w/ 2 workers' called: 5.65s
  Time needed for `FuturesSession w/ max workers' called: 1.25s
  Time needed for `aiohttp' called: 1.19s

• Streaming

Let me tell you about the still-not-defunct real-time log processing pipeline we built at my now-defunct last job. It handled logs from a large number of embedded devices that our ISP operated [...] Eventually our team's log processing system evolved to become the primary monitoring and alerting infrastructure for our ISP.

you mostly get told that you shouldn't be using unstructured logs anyway, you should be using event streams.
That advice is not wrong, but it's incomplete.

There's a file called /dev/kmsg which, if you write to it, produces messages into the kernel's buffer. Let's do that! For all our messages!

RAM is even more volatile than disk, and you have to reboot after a kernel panic. So the RAM is gone, right? Well, no. Sort of. Not exactly.

have the client to stream logs to the server. This is possible using HTTP POST and Chunked encoding,

The log uploader uses a backoff timer so that if it's been trying to upload for a while, it uploads less often. However, the backoff timer was limited to no more than the usual inter-upload interval.

Someone probably told you that log messages are too slow, or too big, or too hard to read, or too hard to use, or you should use them while debugging and then delete them. All those people were living in the past and they didn't have a fancy log pipeline. Computers are really, really fast now. Storage is really, really cheap.

How much are you paying for someone to run some bloaty full-text indexer on all your logs, to save a few milliseconds per grep?

Record, replay, and stub HTTP interactions.

• 🚀 Fetch & XHR Support
• ⚡️️ Simple, Powerful, & Intuitive API
• 💎 First Class Mocha & QUnit Test Helpers
• 🔥 Intercept, Pass-Through, and Attach Events
• 📼 Record to Disk or Local Storage
• ⏱ Slow Down or Speed Up Time

• HTTP/2
• TLS 1.3
• DOH: DNS over HTTP
• QUIC: a candidate replacement for the TCP protocol

  since Google has already deployed QUIC in the Chrome browser and on its sites, it already accounts for more than 7% of Internet traffic.

Also mention this creepy & fascinating attack : http://codebutler.com/firesheep

I love reveal.js. I've been using it for years. But the other day, I was badly bitten by its requirement on a local HTTP server.

What happenned was that I was invited to make a short presentation in a youth and cultural center. I had prepared some slides with …

Simply add the following class to your project. It will be automatically registered at start-up if you use the @EnableAutoConfiguration annotation :

@ControllerAdvice  // Makes this the default behaviour of all controllers
@ConditionalOnProperty(prefix = "app", name = "disable-default-exception-handling")
class GlobalControllerExceptionHandler {
    @ExceptionHandler(Exception.class)  // Catch any exception
    @ResponseStatus(HttpStatus.INTERNAL_SERVER_ERROR)  // Returns an error code …

Often throws "Application error"

Alt:

• https://httpbin.org : HTTP Client Testing Service by Kenneth Reitz
• https://hookbin.com
• https://putsreq.com
• https://www.mocky.io

Internet Explorer Internals and Developer Information

We're the smartest CDN on the planet. That means microsecond response. Unheard of extensibility. Flexibility. Talk to our engineers. Test us. Try us. Free.