Skip to content

Update ajaxforms #5805

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 26, 2024
Merged

Update ajaxforms #5805

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1bfd1f1
Remove 'just'
erikjanwestendorp Jan 24, 2024
8f8aa6a
Remove 'easily'
erikjanwestendorp Jan 24, 2024
4e37288
Update v12
erikjanwestendorp Jan 26, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions 12/umbraco-forms/developer/ajaxforms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -524,7 +524,7 @@ Firstly, with server-to-server integrations you will want to disable the antifor

This is done by setting the `Umbraco:Forms:Security:EnableAntiForgeryTokenForFormsApi` configuration key to a value of `false`.

You should then configure an API key `Umbraco:Forms:Security:FormsApiKey`. This can be any string value, but shouldn't be easily guessable by a brute force attack.
You should then configure an API key `Umbraco:Forms:Security:FormsApiKey`. This can be any string value, but it should be complex enough to resist being guessed by a brute force attack.

With this in place any request to the Forms API will be rejected unless the configured value is provided in an HTTP header named `Api-Key`.

Expand All @@ -538,7 +538,7 @@ Examples demonstrating how to handle a file upload and use reCAPTCHA fields are

The [Content Delivery API](https://docs.umbraco.com/umbraco-cms/v/12.latest/reference/content-delivery-api) provides headless capabilities within Umbraco by allowing you to retrieve content in JSON format.

When retrieving content that contains an Umbraco Forms form picker, the output by default will consist of just the ID of the selected form:
When retrieving content that contains an Umbraco Forms form picker, the output by default will consist of the ID of the selected form:

```json
{
Expand Down
4 changes: 2 additions & 2 deletions 13/umbraco-forms/developer/ajaxforms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -524,7 +524,7 @@ Firstly, with server-to-server integrations you will want to disable the antifor

This is done by setting the `Umbraco:Forms:Security:EnableAntiForgeryTokenForFormsApi` configuration key to a value of `false`.

You should then configure an API key `Umbraco:Forms:Security:FormsApiKey`. This can be any string value, but shouldn't be easily guessable by a brute force attack.
You should then configure an API key `Umbraco:Forms:Security:FormsApiKey`. This can be any string value, but it should be complex enough to resist being guessed by a brute force attack.

With this in place any request to the Forms API will be rejected unless the configured value is provided in an HTTP header named `Api-Key`.

Expand All @@ -538,7 +538,7 @@ Examples demonstrating how to handle a file upload and use reCAPTCHA fields are

The [Content Delivery API](https://docs.umbraco.com/umbraco-cms/v/12.latest/reference/content-delivery-api) provides headless capabilities within Umbraco by allowing you to retrieve content in JSON format.

When retrieving content that contains an Umbraco Forms form picker, the output by default will consist of just the ID of the selected form:
When retrieving content that contains an Umbraco Forms form picker, the output by default will consist of the ID of the selected form:

```json
{
Expand Down