[Question] http request against authorized api:s and server pre-rendering #1447

New Issue

fergalmoran · 2025-08-09T17:20:11Z

fergalmoran commented

2025-08-09 17:20:11 +00:00

Originally created by @baserz on 8/8/2016

Hi folks
Have a question in regards to the prerendering functionality. It seems that when prerendering is run it doesnt recognize for example an active forms session through Identity (where the method is utilizing the Authorize attribute). It will render on the server-side, resulting in a status 401, then rendered again at the client-side (this time successfully).

The question is two-fold. 1: Is there any way of making the prerendering functionality take identity authorization into consideration and if not, is there preferred way (other than buildning control mechanism yourself) which can be used to only run certain ng2 calls / methods if rendered on client-side?

*Originally created by @baserz on 8/8/2016* Hi folks Have a question in regards to the prerendering functionality. It seems that when prerendering is run it doesnt recognize for example an active forms session through Identity (where the method is utilizing the Authorize attribute). It will render on the server-side, resulting in a status 401, then rendered again at the client-side (this time successfully). The question is two-fold. 1: Is there any way of making the prerendering functionality take identity authorization into consideration and if not, is there preferred way (other than buildning control mechanism yourself) which can be used to only run certain ng2 calls / methods if rendered on client-side?

fergalmoran closed this issue

2025-08-09 17:20:11 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1447