Hacktoberfest

Most pull requests have pre-commit checks failing because the author haven't used it.

MuiSwitch doesn't look right if checkbox has position relative. In v4 was possible to resolve using an override:

overrides: { MuiSwitch: { input: { position: 'absolute !important' }, } }

Following documentation to do the same in v5 the code required should be the following:

`components:{
MuiSwitch: {
styleOverrides: {
input: {
po

Proof read transcribed code of UPDATE_PROGRAM against scans

Lines: 548
Page: 1386—1396 (10)

Reduced quality scans can be found here

Since iOS has changed its cookie policy named as INTELLIGENT TRACKING PREVENTION (see risetechnologies/cookieTest#2 (comment) for a brief explanation) cookies set by the server are not being taken into account anymore (also see https://forums.meteor.com/t/sticky-session-using-cookies-and-cordova/44419/9).

This is especially an issue if load balancers use

spider.state is not mentioned on https://docs.scrapy.org/en/latest/topics/spiders.html; it is only mentioned here: https://docs.scrapy.org/en/latest/topics/jobs.html#keeping-persistent-state-between-batches. It'd be nice to document this attribute.

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

Problem to solve

I have a stepped process where the user enters a name for a new object. The validation state of this step relies on name existing. My goal is for the step to be in error when there is no error and not in error when the user has entered an error.

The problem is that when the stepper screen comes up, this step is in error immediately. Good UI design dictates that the step s

Describe the bug
environment <> should be useable within a raw request body, but it isn't

To Reproduce
create an env variable, eg "user"
use it (<>) into url: it works
use it (<>) into the raw request body textarea: it is not replaced with var content

Expected behavior
<> should be replaced with env var content

Screenshots
![image](https:/