Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

SSR in Pages Router vs App Router in Next.js

61,064 görüntüleme • 1 yıl önce •via X (Twitter)

10 Yorum

Andrew Aliaj profil fotoğrafı
Andrew Aliaj1 yıl önce

The App Router is better than the Pages Router.

Austin K profil fotoğrafı
Austin K1 yıl önce

Time to interactive is also faster

Umair profil fotoğrafı
Umair1 yıl önce

Its pretty much the same Alex

Ezequiel Parziale profil fotoğrafı
Ezequiel Parziale1 yıl önce

App router 🚀

ابراهيم | مبرمج profil fotoğrafı
ابراهيم | مبرمج1 yıl önce

Great video 👍👏 how do you record your videos?

notRekash profil fotoğrafı
notRekash1 yıl önce

Mixed with SSG and server action next is very powerful

Nick Muller profil fotoğrafı
Nick Muller1 yıl önce

Although this is fair, I think another interesting comparison would be just rendering the skeleton in the page router, and loading the content client-side. Possibly via TanStack Query.

Krimo profil fotoğrafı
Krimo1 yıl önce

how do you hide those tailwind classes attributes?

Ice.eth profil fotoğrafı
Ice.eth1 yıl önce

Hey! What’s that tailwind logo beside your tag name?

rong-sen-e/acc profil fotoğrafı
rong-sen-e/acc1 yıl önce

TIL performance insights tab

Benzer Videolar

🚨 POC for CVE-2025-55182 that works on Next.js 16.0.6 Here are the exact, battle-tested queries you need — Censys, Shodan, FOFA, ZoomEye, Quake, BinaryEdge, and Nuclei matchers — all tuned specifically to find Next.js RSC / React Server Components instances vulnerable to CVE-2025-55182 (React2Shell). ⸻ ✅ 1. SHODAN QUERY (380K+ ASSETS) Find all servers leaking RSC Server Actions: Basic Query "Vary: RSC, Next-Router-State-Tree" More Aggressive Variant http.headers.vary:"RSC" AND http.headers.vary:"Next-Router-State-Tree" Superwide Coverage "Next-Router-State-Tree" OR "x-nextjs-cache" OR "server-actions" OR "__RSC__" Focused on Vulnerable Cache Indicators "x-nextjs-cache: HIT" "Next-Router-State-Tree" ⸻ ✅ 2. CENSYS QUERY (270K+ ASSETS) (match the screenshot you posted) Exact Censys Search services.http.response.headers.vary: "RSC, Next-Router-State-Tree" Safer Multi-Matcher services.http.response.headers.vary: "RSC" AND services.http.response.headers.vary: "Next-Router-State-Tree" Detect RSC Payload Exposure (critical) services.http.response.body: "__RSC__" Detect Flight Data Leaks services.http.response.body: "server-reference-manifest" ⸻ ✅ 3. FOFA QUERY (CHINA’S OSINT GIANT) (VERY POWERFUL for RSC/Next.js) Exact Header Based header="Next-Router-State-Tree" && header="RSC" Alternative (match screenshot patterns) "Next-Router-State-Tree" && "x-nextjs-cache" For massive result count body="__RSC__" || header="server-actions" ⸻ ✅ 4. ZOOMEYE QUERY ZoomEye scans often catch Node.js apps Shodan misses. Exact Unicode-Ready Query "Next-Router-State-Tree" && "RSC" Advanced app:"Next.js" && header:"RSC" ⸻ ✅ 5. QUAKE SEARCH (360K+ MATCHES) header:"Next-Router-State-Tree" AND header:"RSC" ⸻ ✅ 6. BINARYEDGE QUERY http.response.headers.vary:"Next-Router-State-Tree" ⸻ ✅ 7. QUERY headers:"Next-Router-State-Tree" && headers:"RSC" ⸻ 🎯 8. NUCLEI MATCHER (to detect RSC without scanning payloads) If you want a nuclei detector you can plug into your scanner: matchers: - type: word part: header words: - "RSC" - "Next-Router-State-Tree" - "server-actions" - "__RSC__" ⸻ 🚩 BONUS — THE MOST ADVANCED CROSS-ENGINE QUERY Use this when you want maximum global coverage: "Next-Router-State-Tree" OR "RSC" OR "__RSC__" OR "server-actions" OR "x-nextjs-cache" OR "Next-Server-Action" This identifies: •Next.js App Router •RSC endpoints •Server Actions •Flight data APIs •Pages exposing cache HITs (required for exploitation) •Systems likely vulnerable to CVE-2025-55182 (React2Shell)

X

10,544 görüntüleme • 7 ay önce