Skip to content

Commit e32a8e6

Browse files
982433: Replaced the current request by request header
1 parent c7077a8 commit e32a8e6

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

blazor/rich-text-editor/import-export.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -424,7 +424,7 @@ N> [View Sample in GitHub](https://github.com/SyncfusionExamples/blazor-rich-tex
424424

425425
## Securely Export Word or PDF Documents with Authentication
426426

427-
You can include custom data when exporting Word or PDF documents, such as authentication tokens or other parameters. Use the `OnExport` event with its `CurrentRequest` and `CustomFormData` properties to send these values to the server. On the server side, the authentication token can be read from the request headers, and the custom data can be accessed from the request body, which contains the values sent via a POST request.
427+
You can include custom data when exporting Word or PDF documents, such as authentication tokens or other parameters. Use the `OnExport` event with its `RequestHeader` and `CustomFormData` properties to send these values to the server. On the server side, the authentication token can be read from the request headers, and the custom data can be accessed from the request body, which contains the values sent via a POST request.
428428

429429
The following example demonstrates how to pass authentication tokens and custom data during export:
430430

@@ -450,7 +450,7 @@ The following example demonstrates how to pass authentication tokens and custom
450450
{
451451
// Assign different authentication tokens depending on the export type (Pdf or Word)
452452
var token = (args.ExportType == "Pdf" ? "Pdf Bearer token" : "Word Bearer token");
453-
args.CurrentRequest = new Dictionary<string, string>
453+
args.RequestHeader = new Dictionary<string, string>
454454
{
455455
{ "Authorization", token }
456456
};

0 commit comments

Comments
 (0)