Middleware for authentication in Astro - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is middleware in the context of web frameworks like Astro?

Middleware is a function that runs between a user's request and the server's response. It can modify requests, responses, or control access before reaching the main handler.

beginner

Why use middleware for authentication?

Middleware for authentication checks if a user is logged in before allowing access to certain pages or APIs. It helps protect private content easily and consistently.

intermediate

How does Astro middleware handle redirecting unauthenticated users?

If a user is not authenticated, the middleware can send a redirect response to a login page, stopping the request from reaching protected content.

intermediate

What is a common way to check authentication status in Astro middleware?

A common way is to check cookies or headers for a valid token or session ID that proves the user is logged in.

beginner

Give a simple example of middleware for authentication in Astro.

Middleware checks if a cookie named 'authToken' exists. If missing, it redirects to '/login'. If present, it allows the request to continue.

What does authentication middleware do in Astro?

A Fetches data from a database

B Styles the webpage

C Checks if a user is logged in before accessing a page

D Handles image uploads

Authentication middleware controls access by verifying if the user is logged in.

Where does middleware run in the request process?

A Only during page rendering

B After the server sends the response

C Only on the client side

D Before the request reaches the main handler

Middleware runs between the incoming request and the main handler to process or block requests.

If a user is not authenticated, what should middleware do?

A Redirect to a login page

B Delete the user account

C Allow access to all pages

D Send a success message

Redirecting unauthenticated users to login protects private content.

Which of these is a common way to identify an authenticated user in middleware?

A Checking a cookie or token

B Checking the user's screen size

C Checking the browser's color scheme

D Checking the user's IP address only

Cookies or tokens are used to verify user identity in authentication middleware.

In Astro, what happens if middleware allows the request to continue?

A The request is blocked

B The request reaches the protected page or API

C The server crashes

D The user is logged out

Allowing the request means the user can access the protected resource.

Explain how middleware can protect private pages in Astro.

Think about what happens before the page loads.

Describe a simple way to implement authentication middleware in Astro.

Focus on checking user login state.

Practice

1. What is the main purpose of middleware for authentication in Astro?

easy

A. To fetch data from an external API after the page loads

B. To style the webpage with CSS before rendering

C. To check if a user is allowed to access certain pages before loading them

D. To optimize images automatically during build

Solution

1. Step 1: Understand middleware role

   Middleware runs before page loads to control access.

2. Step 2: Identify authentication purpose

   Authentication middleware checks user identity to allow or block access.

3. Final Answer:

   To check if a user is allowed to access certain pages before loading them -> Option C

4. Quick Check:

   Middleware controls access = A [OK]

Hint: Middleware controls access before page loads [OK]

Common Mistakes:

• Confusing middleware with styling or data fetching
• Thinking middleware runs after page loads
• Assuming middleware optimizes images

2. Which is the correct way to allow access to the next middleware or page in Astro authentication middleware?

easy

A. return context.stop()

B. return context.skip()

C. return context.block()

D. return context.next()

Solution

1. Step 1: Recall middleware flow control

   In Astro, calling context.next() passes control to next middleware or page.

2. Step 2: Identify correct method to continue

   Only context.next() allows access; others are invalid or block.

3. Final Answer:

   return context.next() -> Option D

4. Quick Check:

   Allow access = context.next() [OK]

Hint: Use context.next() to continue middleware chain [OK]

Common Mistakes:

• Using non-existent methods like context.stop()
• Confusing block and skip with next
• Omitting return keyword

3. Given this Astro middleware code snippet, what happens if the user is not authenticated?

export async function middleware(context) {
  if (!context.cookies.get('authToken')) {
    return new Response('Unauthorized', { status: 401 });
  }
  return context.next();
}

medium

A. The user sees a 401 Unauthorized response and page does not load

B. The user is redirected to the homepage

C. The middleware ignores the check and loads the page

D. The user is logged out automatically

Solution

1. Step 1: Analyze authentication check

   The code checks if 'authToken' cookie exists; if not, returns 401 response.

2. Step 2: Understand middleware response effect

   Returning a Response with status 401 stops page loading and shows unauthorized message.

3. Final Answer:

   The user sees a 401 Unauthorized response and page does not load -> Option A

4. Quick Check:

   Missing authToken = 401 response [OK]

Hint: Return Response with 401 to block unauthorized users [OK]

Common Mistakes:

• Assuming middleware redirects automatically
• Thinking page loads despite 401 response
• Confusing logout with blocking access

4. Identify the error in this Astro middleware code for authentication:

export async function middleware(context) {
  if (!context.cookies.get('authToken')) {
    context.next();
  }
  return new Response('Unauthorized', { status: 401 });
}

medium

A. The Response status 401 should be 200 to allow access

B. context.next() is called but its result is not returned, so middleware blocks all requests

C. The cookie name 'authToken' is incorrect and causes a runtime error

D. Middleware functions cannot be async in Astro

Solution

1. Step 1: Check middleware flow control

   context.next() must be returned to continue; here it is called but not returned.

2. Step 2: Understand effect of missing return

   Since return is after if-block, middleware always returns 401 response, blocking all requests.

3. Final Answer:

   context.next() is called but its result is not returned, so middleware blocks all requests -> Option B

4. Quick Check:

   Return context.next() to allow access [OK]

Hint: Always return context.next() to continue middleware chain [OK]

Common Mistakes:

• Calling context.next() without return
• Misunderstanding cookie name importance
• Thinking async is disallowed in middleware

5. You want to protect multiple private routes in Astro using middleware. Which approach correctly applies authentication middleware only to URLs starting with /dashboard or /settings?

hard

A. Check if context.url.pathname starts with '/dashboard' or '/settings' and run auth check only then

B. Apply middleware globally and always block access regardless of URL

C. Use middleware only on the homepage '/' to protect all routes

D. Check if context.url.pathname ends with '/dashboard' or '/settings' to run auth

Solution

1. Step 1: Understand route matching in middleware

   Middleware can check context.url.pathname to target specific routes.

2. Step 2: Identify correct string method for prefix matching

   Using startsWith matches routes beginning with '/dashboard' or '/settings'.

3. Step 3: Evaluate other options

   Blocking all routes or checking endsWith is incorrect for this purpose.

4. Final Answer:

   Check if context.url.pathname starts with '/dashboard' or '/settings' and run auth check only then -> Option A

5. Quick Check:

   Use startsWith for route prefix matching [OK]

Hint: Use startsWith to target route prefixes in middleware [OK]

Common Mistakes:

• Blocking all routes instead of specific ones
• Using endsWith instead of startsWith
• Applying middleware only on homepage