location

The date and time that the message was sent.

date

The length of the response body in octets (8-bit bytes).

content-length

This and all future requests should be directed to the given URI. This is similar to 301 but the request method cannot change.

Inform all caching mechanisms from server to client whether they may cache this object.

cache-control

The content security policy allows the server to determine what resources the user is allowed to load.

default-src

Define what can be used in the base element.

base-uri

connect-src

font-src

manifest-src

frame-src

img-src

script-src

style-src

Define sources for object, embed, and applet elements.

object-src

Define what can be used as the target for forms.

form-action

Define sources for audio, video, and track elements.

media-src

Treat insecure URLs as though they are secure.

content-security-policy

type

description

charset

content-type

An identifier for a specific version of a resource.

A weak tag is easier to generate and prevents byte range caching.

validator

etag

hedgedoc-version

Controls what referrer information is sent with requests.

Send the full referrer for same origin requests, and nothing for cross-origin.

referrer-policy

A cookie sent from the server to be set on the client

connect.sid

The client will only send the cookie when requesting this path, or subdirectories, from the server.

Path

Expires

Prevents access to the cookie through JavaScript.

The cookie is only sent when requesting from a https domain.

Cookie is not sent on cross-site requests but is when following a link to the origin.

SameSite

set-cookie

A HSTS Policy informing the HTTP client how long to cache the HTTPS only policy and whether this applies to subdomains.

The time a browser should remember a site can only be accessed with https (seconds).

max-age

strict-transport-security

Indicates that different content may be provided to different clients, depending on the vary header.

headers

vary

x-powered-by

Standard response indicating a successful action. For GET requests this will be the resource, and for POST it will be the result of the action.

HTTP Headers

Summary

Details

`https://pad.stuve.uni-ulm.de/s/cJYewZ-Lb`

`https://pad.stuve.de/s/cJYewZ-Lb`