OXIESEC PANEL
- Current Dir:
/
/
var
/
www
/
reader
/
API
/
swagger-ui-5.17.14
/
docs
/
usage
Server IP: 139.59.38.164
Upload:
Create Dir:
Name
Size
Modified
Perms
📁
..
-
08/07/2024 04:33:52 AM
rwxr-xr-x
📄
configuration.md
18.06 KB
08/07/2024 04:33:48 AM
rw-r--r--
📄
cors.md
2.69 KB
08/07/2024 04:33:48 AM
rw-r--r--
📄
deep-linking.md
1.75 KB
08/07/2024 04:33:48 AM
rw-r--r--
📄
installation.md
6.2 KB
08/07/2024 04:33:48 AM
rw-r--r--
📄
limitations.md
845 bytes
08/07/2024 04:33:48 AM
rw-r--r--
📄
oauth2.md
2.4 KB
08/07/2024 04:33:48 AM
rw-r--r--
📄
version-detection.md
2.52 KB
08/07/2024 04:33:48 AM
rw-r--r--
Editing: limitations.md
Close
# Limitations ### Forbidden header names Some header names cannot be controlled by web applications, due to security features built into web browsers. Forbidden headers include: > - Accept-Charset > - Accept-Encoding > - Access-Control-Request-Headers > - Access-Control-Request-Method > - Connection > - Content-Length > - Cookie > - Cookie2 > - Date > - DNT > - Expect > - Host > - Keep-Alive > - Origin > - Proxy-* > - Sec-* > - Referer > - TE > - Trailer > - Transfer-Encoding > - Upgrade > - Via > > _[Forbidden header names (developer.mozilla.org)](https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name)_ The biggest impact of this is that OpenAPI 3.0 Cookie parameters cannot be controlled when running Swagger UI in a browser. For more context, see [#3956](https://github.com/swagger-api/swagger-ui/issues/3956).