EndpointSource Pennington.Pipeline
Marker source for routes whose content is produced by a live HTTP endpoint (e.g., a custom IContentService page or an AddTaxonomy term page). These items exist so the build crawler discovers the URL and fetches it through the live pipeline — they do not participate in parse/render and are not redirects. Because the endpoint serves real canonical HTML at a stable URL, the route is listed in the sitemap; transport endpoints that emit a non-HTML file are dropped earlier by SitemapService's output-extension check.
Constructors
EndpointSource
#public EndpointSource()
Marker source for routes whose content is produced by a live HTTP endpoint (e.g., a custom IContentService page or an AddTaxonomy term page). These items exist so the build crawler discovers the URL and fetches it through the live pipeline — they do not participate in parse/render and are not redirects. Because the endpoint serves real canonical HTML at a stable URL, the route is listed in the sitemap; transport endpoints that emit a non-HTML file are dropped earlier by SitemapService's output-extension check.
Pennington.Pipeline.EndpointSource
namespace Pennington.Pipeline;
/// Marker source for routes whose content is produced by a live HTTP endpoint (e.g., a custom IContentService page or an AddTaxonomy term page). These items exist so the build crawler discovers the URL and fetches it through the live pipeline — they do not participate in parse/render and are not redirects. Because the endpoint serves real canonical HTML at a stable URL, the route is listed in the sitemap; transport endpoints that emit a non-HTML file are dropped earlier by SitemapService's output-extension check.
public record EndpointSource
{
/// Marker source for routes whose content is produced by a live HTTP endpoint (e.g., a custom IContentService page or an AddTaxonomy term page). These items exist so the build crawler discovers the URL and fetches it through the live pipeline — they do not participate in parse/render and are not redirects. Because the endpoint serves real canonical HTML at a stable URL, the route is listed in the sitemap; transport endpoints that emit a non-HTML file are dropped earlier by SitemapService's output-extension check.
public EndpointSource()
;
}