Purpose of this repository is to practise theoretical knowledge and build portfolio usecase website.
- I focus here more on backend development
- I have many years of practise building frontend website from scratch with html, css, js.
- I worked as manager for jewelry eshop, ecommerce prestashop open source, micro photography of jewelry, photo editing, frontend editing,
- I have a strong knowledge of Domain name system,
- I have my own name servers
- I am official domain fi registrator
- I am changing my profesion from automotive industry to IT industry because it is my long term plan
- I would like to work from home, remotely
My second interest is to practice databases, sql language, practise ORM libraries ( Prime, Knex, ... )
My third interest is to practise payment system implementation. I already build eshop with Stripe payment
Subprojects:
WebAuthn ( Web Authentication API ) is extention of Credential Managment API
- I use pnpm package manager
- .gitignore file is included
- I use Pug template engine >> PUG-TEMPLATE-ENGINE.md
- I do not use yet Consolidate to use React as template engine
https://datatracker.ietf.org/doc/html/rfc7231 - HTTP Semantics and Content
- representation is information
- Content-Type
- Content-Encoding
- Content-Language
- Content-Location
Representation header fields provide metadata about the representation. When a message includes a payload body, the representation header fields describe how to interpret the representation data enclosed in the payload body. In a response to a HEAD request, the representation header fields describe the representation data that would have been enclosed in the payload body if the same request had been a GET.
Data type of representation data is determined via the header fields:
- Content-Type
- Content-Encoding
- Content-Length
- Content-Range
- Trailer
- Transfer-Encoding
- proactive, where the server selects the representation based upon the user agent's stated preferences
- reactive, where the server provides a list of representations for the user agent to choose from
- conditional content
- active content
+---------+-------------------------------------------------+-------+ | Method | Description | Sec. | +---------+-------------------------------------------------+-------+ | GET | Transfer a current representation of the target | 4.3.1 | | | resource. | | | HEAD | Same as GET, but only transfer the status line | 4.3.2 | | | and header section. | | | POST | Perform resource-specific processing on the | 4.3.3 | | | request payload. | | | PUT | Replace all current representations of the | 4.3.4 | | | target resource with the request payload. | | | DELETE | Remove all current representations of the | 4.3.5 | | | target resource. | | | CONNECT | Establish a tunnel to the server identified by | 4.3.6 | | | the target resource. | | | OPTIONS | Describe the communication options for the | 4.3.7 | | | target resource. | | | TRACE | Perform a message loop-back test along the path | 4.3.8 | | | to the target resource. | | +---------+-------------------------------------------------+-------+
// CONTINUE HERE https://datatracker.ietf.org/doc/html/rfc7231#section-4.3.3