How do you work with requests and responses?

Question

Accepted Answer

Laravel wraps HTTP in convenient **Request** and **Response** objects. The `Request` object provides safe, clean access to incoming data (input, files, headers); Laravel's response helpers make returning views, JSON, redirects, and more straightforward.

## Accessing request data

```php
public function store(Request $request) {
    $request->input('name');             // a specific input field
    $request->name;                       // shorthand access
    $request->only(['name', 'email']);    // a subset
    $request->all();                      // all input
    $request->query('sort');              // a query string param (?sort=)
    $request->has('email');               // check presence
    $request->input('page', 1);           // with a default

$request->file('avatar');             // an uploaded file
    $request->header('Authorization');
    $request->user();                     // the authenticated user
    $request->ip(); $request->method();   // request metadata
}
```

The `Request` object (auto-injected into controller methods) gives clean, safe access to all incoming data — far better than raw `$_GET`/`$_POST` superglobals, with helper methods for common needs.

## Returning responses

```php
return view('users.index', ['users' => $users]);   // render a Blade view
return response()->json($data, 200);                // JSON (auto for arrays/models too)
return $user;                                       // a model → auto-serialized to JSON
return redirect('/home');                            // redirect
return redirect()->route('profile')->with('msg', 'Saved!');   // redirect + flash message
return back();                                       // redirect to the previous page
return response()->download($path);                  // file download
```

Laravel's response helpers handle the common cases elegantly: rendering views, returning JSON (arrays and Eloquent models auto-serialize to JSON), redirects (with flash messages), and downloads. Returning a model or array from a controller automatically produces a JSON response.

## Customizing responses

```php
return response()->json(['error' => 'Not found'], 404)
    ->header('X-Custom', 'value');                   // custom status + headers
return response('Hello', 200)->header('Content-Type', 'text/plain');
```

## Why it matters

Working with requests and responses is fundamental to every Laravel application — handling incoming data and returning output is the core of request processing, so understanding these objects is essential everyday knowledge.

The **Request object** provides clean, safe, convenient access to all incoming data (input, query params, files, headers, the authenticated user) through helpful methods — a major improvement over raw PHP superglobals (`$_GET`/`$_POST`), both in ergonomics and in encouraging safe handling.

Laravel's **response helpers** make returning all common response types elegant: rendering Blade views, returning JSON (with arrays and Eloquent models automatically serialized — convenient for APIs), redirects (with flash messages for user feedback), file downloads, and custom responses with specific status codes and headers.

Understanding how to access request data through the Request object's methods and how to return the appropriate response type (views for web pages, JSON for APIs, redirects after actions) is core, must-know knowledge for building any Laravel endpoint, since every controller method receives a request and returns a response.

The convenience and safety of Laravel's request/response abstractions are part of what makes the framework productive, and fluency with them is foundational to effective Laravel development.