Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

SSR in Pages Router vs App Router in Next.js

61,064 Aufrufe • vor 2 Jahren •via X (Twitter)

10 Kommentare

Profilbild von Andrew Aliaj
Andrew Aliajvor 2 Jahren

The App Router is better than the Pages Router.

Profilbild von Austin K
Austin Kvor 2 Jahren

Time to interactive is also faster

Profilbild von Umair
Umairvor 2 Jahren

Its pretty much the same Alex

Profilbild von Ezequiel Parziale
Ezequiel Parzialevor 2 Jahren

App router 🚀

Profilbild von ابراهيم | مبرمج
ابراهيم | مبرمجvor 2 Jahren

Great video 👍👏 how do you record your videos?

Profilbild von notRekash
notRekashvor 2 Jahren

Mixed with SSG and server action next is very powerful

Profilbild von Nick Muller
Nick Mullervor 2 Jahren

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.

Profilbild von Krimo
Krimovor 2 Jahren

how do you hide those tailwind classes attributes?

Profilbild von Ice.eth
Ice.ethvor 2 Jahren

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

Profilbild von rong-sen-e/acc
rong-sen-e/accvor 2 Jahren

TIL performance insights tab

Ähnliche Videos

🚨 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 Aufrufe • vor 10 Monaten