Skip to content
This repository has been archived by the owner on Nov 28, 2019. It is now read-only.

Commit

Permalink
Fixed a typo (#200)
Browse files Browse the repository at this point in the history
  • Loading branch information
aalok05 authored and ardalis committed Jan 15, 2018
1 parent 486fd86 commit 22fbddd
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions content/asp.net/getting-started/middleware-basic.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,10 +139,10 @@ app.Use(async (context, next) =>
```

> **Note** {.note}
> Avoid writing to Response headers in middleware if you're not certain that other middleware hasn't already begun writing to the response (in which case, the headers will already have been sent to the client). In particular, use caution when writing to the Response after having called other middleware (in the example above, aftet the ``await next();`` statement).
> Avoid writing to Response headers in middleware if you're not certain that other middleware hasn't already begun writing to the response (in which case, the headers will already have been sent to the client). In particular, use caution when writing to the Response after having called other middleware (in the example above, after the ``await next();`` statement).
## Next Steps

See if you can create another request endpoint to display a particular quotation. You can do this by using ``app.Map`` for a particular path, such as ``/quote``. Notice that within a mapped pipeline, the path segment used to match ``app.Map`` is removed from the ``Request.Path``. Thus, if you map ``/quote`` and want to pull the index of the quote from the full path of ``/quote/1``, you'll find that within your ``Map`` function the path is simply ``/1``.

You can fetch a specific quotation by index using, for example, ``QuotationStore.Quotations[0]``.
You can fetch a specific quotation by index using, for example, ``QuotationStore.Quotations[0]``.

0 comments on commit 22fbddd

Please sign in to comment.