Why authentication needs server-side logic in Astro - Performance Evidence

Performance: Why authentication needs server-side logic

HIGH IMPACT

This affects page load speed and interaction responsiveness by controlling secure data flow and reducing client-side processing.

Implementing user login securely

Astro

// src/pages/api/login.js
export async function POST({ request, cookies }) {
  const formData = await request.formData();
  const username = formData.get('username');
  const password = formData.get('password');
  const valid = await verifyUserOnServer(username, password);
  if (valid) {
    // Set secure HTTP-only cookie
    cookies.set('auth', 'true', {
      httpOnly: true,
      secure: true,
      sameSite: 'strict'
    });
    return new Response(JSON.stringify({ success: true }), { status: 200, headers: { 'Content-Type': 'application/json' } });
  }
  return new Response(JSON.stringify({ success: false }), { status: 401, headers: { 'Content-Type': 'application/json' } });
};

Runs authentication on the server, reducing client load and securing credentials from exposure.

📈 Performance GainImproves interaction responsiveness (INP) by offloading heavy logic; prevents security-related rework.

Implementing user login securely

Astro

const login = (username, password) => {
  // Client-side only authentication
  if (username === 'user' && password === 'pass') {
    localStorage.setItem('auth', 'true');
    return true;
  }
  return false;
};

This exposes sensitive logic and credentials to the client, risking security and allowing manipulation.

📉 Performance CostBlocks interaction with insecure client-side checks; causes security risks that can lead to costly breaches.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Client-side authentication	Minimal DOM changes	0 reflows	Low paint cost	[X] Bad - security risk and blocks interaction
Server-side authentication	Minimal DOM changes	0 reflows	Low paint cost	[OK] Good - secure and responsive

Rendering Pipeline

Authentication logic on the server avoids blocking client rendering and interaction by handling sensitive checks before sending responses.

→Network

→JavaScript Execution

→Interaction Handling

⚠️ BottleneckClient-side JavaScript Execution when authentication is done on client

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness by controlling secure data flow and reducing client-side processing.

Optimization Tips

1Always run authentication logic on the server to protect sensitive data.

2Avoid heavy client-side authentication to keep input responsiveness high.

3Use secure HTTP-only cookies set by the server to manage sessions safely.

Performance Quiz - 3 Questions

Why is server-side authentication better for performance?

A It reduces client CPU load and improves input responsiveness.

B It increases client-side JavaScript execution time.

C It causes more reflows and repaints on the page.

D It delays network requests unnecessarily.

DevTools: Performance

How to check: Record a session while performing login; check for long scripting tasks or blocked input during authentication.

What to look for: Look for long tasks blocking main thread and delayed input responsiveness indicating client-side heavy auth.

Practice

1. Why is authentication usually handled on the server side in web applications?

easy

A. Because authentication does not need any security

B. Because the server can securely check user credentials and control access

C. Because the client can decide who is allowed without server help

D. Because the client can store passwords safely

Solution

1. Step 1: Understand the role of server in authentication

   The server securely stores user data and verifies credentials to protect sensitive information.

2. Step 2: Recognize client limitations

   The client cannot be trusted to securely store or verify credentials because it can be manipulated.

3. Final Answer:

   Because the server can securely check user credentials and control access -> Option B

4. Quick Check:

   Server handles security = D [OK]

Hint: Server controls access securely, client just sends info [OK]

Common Mistakes:

• Thinking client can safely store passwords
• Believing client can decide access alone
• Ignoring security risks on client side

2. Which of the following is the correct way to send user login data from client to server in Astro?

easy

A. fetch('/login', { method: 'GET', body: JSON.stringify({username, password}) })

B. fetch('/login', { method: 'POST', body: username + password })

C. fetch('/login', { method: 'POST', body: JSON.stringify({username, password}) })

D. fetch('/login', { method: 'POST' })

Solution

1. Step 1: Identify correct HTTP method for sending login data

   Login data should be sent using POST to keep data in the request body, not URL.

2. Step 2: Check data format in request body

   Data should be JSON stringified for proper parsing on server side.

3. Final Answer:

   fetch('/login', { method: 'POST', body: JSON.stringify({username, password}) }) -> Option C

4. Quick Check:

   POST with JSON body = B [OK]

Hint: Use POST and JSON.stringify for login data [OK]

Common Mistakes:

• Using GET method which exposes data in URL
• Sending raw concatenated strings instead of JSON
• Omitting the request body

3. Given this Astro server code snippet handling login:

export async function post({ request }) {
  const { username, password } = await request.json();
  if (username === 'user' && password === 'pass') {
    return new Response('Success', { status: 200 });
  } else {
    return new Response('Fail', { status: 401 });
  }
}

What will the server respond if the client sends username='user' and password='wrong'?

medium

A. Fail with status 401

B. Success with status 200

C. Error with status 500

D. No response

Solution

1. Step 1: Check the condition for successful login

   The server checks if username is 'user' and password is 'pass' exactly.

2. Step 2: Evaluate given input against condition

   Input password is 'wrong', which does not match 'pass', so condition fails.

3. Final Answer:

   Fail with status 401 -> Option A

4. Quick Check:

   Wrong password = 401 Fail [OK]

Hint: Match exact username and password on server [OK]

Common Mistakes:

• Assuming any password works
• Confusing status codes
• Ignoring the else branch

4. This Astro server code is meant to authenticate users but has a bug:

export async function post({ request }) {
  const { username, password } = await request.json();
  if (username = 'admin' && password = '1234') {
    return new Response('Logged in', { status: 200 });
  }
  return new Response('Unauthorized', { status: 401 });
}

What is the bug and how to fix it?

medium

A. Use '===' instead of '=' in the if condition

B. Remove the await keyword

C. Use '==' instead of '=' in the if condition

D. Change Response to JSON response

Solution

1. Step 1: Identify incorrect operator in condition

   The code uses '=' which is assignment, not comparison, causing a bug.

2. Step 2: Use strict equality '===' for comparison in JavaScript

   Replace '=' with '===' to correctly compare values in the if condition.

3. Final Answer:

   Use '===' instead of '=' in the if condition -> Option A

4. Quick Check:

   Comparison needs '===' not '=' [OK]

Hint: Use '===' for comparison, '=' is assignment [OK]

Common Mistakes:

• Confusing assignment '=' with comparison '==' or '==='
• Removing await which is needed
• Changing response type unnecessarily

5. You want to protect a private Astro page so only logged-in users can see it. Which server-side approach is best to check authentication before rendering?

hard

A. Render the page fully and then ask for login

B. Check a JavaScript variable on the client to hide content

C. Use client-side localStorage to store login status

D. Check a session cookie on the server and redirect if missing

Solution

1. Step 1: Understand server-side protection needs

   Server must verify user identity before sending private content to prevent unauthorized access.

2. Step 2: Use session cookies for authentication

   Session cookies are sent with requests and can be checked on the server to confirm login status.

3. Final Answer:

   Check a session cookie on the server and redirect if missing -> Option D

4. Quick Check:

   Server checks session cookie before rendering [OK]

Hint: Always verify login on server before showing private pages [OK]

Common Mistakes:

• Relying on client-side checks only
• Using localStorage which can be manipulated
• Rendering private content before login check