How twitter.com Redirects to x.com (The Magic Behind URL Forwarding)

chintanpuggalok — Sun, 29 Dec 2024 04:57:57 +0000

Introduction

Have you ever wondered how twitter.com redirects to x.com? Let's explore this fascinating process using our browser's network console.

As you can see, the request starts from twitter.com and then gets redirected to x.com")

twitter.com redirects to x.com with a status code of 302")

When you visit twitter.com, it first responds with a 302 status code and then redirects to x.com. This process is known as URL forwarding.

What is URL Forwarding?

URL forwarding refers to the act of redirecting from one URL (e.g., url1.com) to another URL (e.g., url2.com).

Learn more about HTTP Redirections on MDN Web Docs

Types of URL Forwarding

Temporary Forwarding

Temporary forwarding is used during site maintenance or downtime. It uses HTTP code 302.

Permanent Forwarding

Permanent forwarding uses HTTP code 301. It is used to preserve existing links/bookmarks after changing the site's URLs, progress pages when uploading a file, etc.

Personal Experience with URL Forwarding

I encountered URL forwarding when setting up x.chintanpuggalok.com to forward to x.com/chintanpuggalok. (DM me if you read this :;)

How to Set Up URL Forwarding Across Different Domains

Here is how you can set up URL forwarding for different domain registrars:

Porkbun: How to set up URL forwarding
Namecheap: How to set up a URL redirect for a domain
Cloudflare: How to set up URL forwarding

Conclusion

Understanding URL forwarding is crucial for web developers and site administrators. It ensures seamless user experience and preserves SEO value when URLs change. Whether it's temporary or permanent, knowing how to set up URL forwarding can be highly beneficial.

Implementing Context Propagation in Reactive Programming Projects 🔄

chintanpuggalok — Tue, 06 Feb 2024 16:57:24 +0000

Learn how to seamlessly propagate context through a reactive stream in your project using Project Reactor, an essential skill for modern Java developers working with reactive programming models.

Mono<DemoClass> demoClassMono = Mono.just(demoObject)
    // Add context to MDC (Mapped Diagnostic Context) for logging purposes on each signal 📋
    .doOnEach(signal -> {
        logUtil.addToMdc(signal.getContextView());
    })
    // Transform the Mono stream by applying a function to each item emitted 🔄
    .transform(demoClassMono1 -> {
        log.info("inside main post init {}", demoClassMono1.toString());
        return another.anotherDemoProcess(demoClassMono1);
    })
    // Write context information by adding header details to the Reactor context ✍
    .contextWrite(context -> {
        return context.putAllMap(headerDetails);
    });

Key Concepts Explained 🔑

.doOnEach((signal) -> {...}): This operator allows for side-effects, such as logging, to be performed for each signal (onNext, onError, onComplete) in the stream. Utilizing logUtil.addToMdc(signal.getContextView()) ensures that every emitted item enriches the Mapped Diagnostic Context (MDC), making it easier to trace and debug reactive chains. 📊
.contextWrite(context -> {...}): By leveraging this operator, developers can modify the context propagated down the stream. Adding key-value pairs from the headerDetails map into the Reactor context with context.putAllMap(headerDetails) is a powerful way to include essential metadata, like request IDs or user tokens, throughout the reactive pipeline. 🔧

Why It Matters in Reactive Programming 🌟

Understanding and implementing context propagation in reactive programming is pivotal for maintaining a clear and traceable execution flow, especially in complex, asynchronous systems. These techniques improve debugging, logging, and the management of metadata across asynchronous boundaries, enhancing the overall reliability and maintainability of applications built with Project Reactor.

here is a Git repo for an example
Git repo for context propagation

DEV Community: chintanpuggalok