主頁 > .NET開發 > IdentityServer4原始碼決議_2_元資料介面

IdentityServer4原始碼決議_2_元資料介面

2020-09-16 04:01:14 .NET開發

目錄

  • IdentityServer4原始碼決議_1_專案結構
  • IdentityServer4原始碼決議_2_元資料介面
  • IdentityServer4原始碼決議_3_認證介面
  • IdentityServer4原始碼決議_4_令牌發放介面
  • IdentityServer4原始碼決議_5_查詢用戶資訊介面
  • [IdentityServer4原始碼決議_6_結束會話介面]
  • [IdentityServer4原始碼決議_7_查詢令牌資訊介面]
  • [IdentityServer4原始碼決議_8_撤銷令牌介面]

協議

這一系列我們都采用這樣的方式,先大概看下協議,也就是需求描述,然后看idsv4怎么實作的,這樣可以加深理解,
元資料介面的協議地址如下:

https://openid.net/specs/openid-connect-discovery-1_0.html

摘要

該協議定義了一套標準,用戶能夠獲取到oidc服務的基本資訊,包括OAuth2.0相關介面地址,

Webfinger - 網路指紋

先了解一下Webfinger這個概念,

WebFinger可以翻譯成網路指紋,它定義了一套標準,描述如何通過標準的HTTP方法去獲取網路物體的資料資訊,WebFinger使用JSON來描述物體資訊,

https://tools.ietf.org/html/rfc7033

查詢oidc服務元資料 - OpenID Provider Issuer Discovery

可選協議,
定義了如何獲取oidc服務元資料,如果客戶端明確知道oidc服務的地址,可以跳過此部分,
個人理解是存在多個oidc服務的情況,可以部署一個webfinger服務,根據資源請求,路由到不同的oidc服務,
通常來說,我們只有一個oidc服務,我看了一下idsv4也沒有實作這一部分協議,這里了解一下就可以了,

查詢oidc服務配置資訊 - OpenID Provider Configuration Request

必選協議,
用于描述oidc服務各介面地址及其他配置資訊,

  GET /.well-known/openid-configuration HTTP/1.1
  Host: example.com

必須校驗issuer與請求地址是否一致

啟個idsrv服務呼叫試一下,回傳結果如圖
image

詳細資訊如下,

{
    "issuer": "https://localhost:10000", //頒發者地址
    "jwks_uri": "https://localhost:10000/.well-known/openid-configuration/jwks", //jwks介面地址,查詢密鑰
    "authorization_endpoint": "https://localhost:10000/connect/authorize", //認證介面地址
    "token_endpoint": "https://localhost:10000/connect/token", //令牌發放介面
    "userinfo_endpoint": "https://localhost:10000/connect/userinfo", //查詢用戶資訊介面
    "end_session_endpoint": "https://localhost:10000/connect/endsession", //結束會話介面
    "check_session_iframe": "https://localhost:10000/connect/checksession", //檢查會話介面
    "revocation_endpoint": "https://localhost:10000/connect/revocation", //撤銷令牌介面
    "introspection_endpoint": "https://localhost:10000/connect/introspect", //查詢令牌詳情介面
    "device_authorization_endpoint": "https://localhost:10000/connect/deviceauthorization", //設備認證介面
    "frontchannel_logout_supported": true, //是否支持前端登出
    "frontchannel_logout_session_supported": true, //是否支持前端結束會話
    "backchannel_logout_supported": true, //是否支持后端登出
    "backchannel_logout_session_supported": true, //是否支持后端結束會話
    "scopes_supported": [ //支持的授權范圍,scope
        "openid",
        "profile",
        "userid",
        "username",
        "email",
        "mobile",
        "api",
        "offline_access" //token過期可用refresh_token重繪換取新token
    ],
    "claims_supported": [ //支持的宣告
        "sub",
        "updated_at",
        "locale",
        "zoneinfo",
        "birthdate",
        "gender",
        "preferred_username",
        "picture",
        "profile",
        "nickname",
        "middle_name",
        "given_name",
        "family_name",
        "website",
        "name",
        "userid",
        "username",
        "email",
        "mobile"
    ],
    "grant_types_supported": [ //支持的認證型別
        "authorization_code", //授權碼模式
        "client_credentials", //客戶端密鑰模式
        "refresh_token", //重繪token
        "implicit", //隱式流程, 一般用于單頁應用javascript客戶端
        "password", //用戶名密碼模式
        "urn:ietf:params:oauth:grant-type:device_code" //設備授權碼
    ],
    "response_types_supported": [ //支持的回傳型別
        "code", //授權碼 
        "token", //通行令牌
        "id_token", //身份令牌
        "id_token token", //身份令牌+統通行令牌
        "code id_token", //授權碼+身份令牌
        "code token", //授權碼+通行令牌
        "code id_token token" //授權碼+身份令牌+通行令牌
    ],
    "response_modes_supported": [ //支持的回應方法
        "form_post", //form-post提交
        "query", //get提交
        "fragment" //fragment提交
    ],
    "token_endpoint_auth_methods_supported": [ //發放令牌介面支持的認證方式
        "client_secret_basic", //basic
        "client_secret_post" //post
    ],
    "id_token_signing_alg_values_supported": [ //身份令牌加密演算法
        "RS256"
    ],
    "subject_types_supported": [
        "public"
    ],
    "code_challenge_methods_supported": [
        "plain",
        "S256"
    ],
    "request_parameter_supported": true
}

JWK - Json Web Keys

idsv還注入這樣一個介面:DiscoveryKeyEndpoint,嘗試發現回傳了一組密鑰,協議內容如下,

https://tools.ietf.org/html/draft-ietf-jose-json-web-key-41

GET /.well-known/openid-configuration/jwks,回傳結果如下

{
    "keys": [
        {
            "kty": "RSA",
            "use": "sig",
            "kid": "LS-EQOr-3BkalkkUVh8q7Q",
            "e": "AQAB",
            "n": "08BLLaTz4JrTYmE4bZ9c7oKVrZKLy3KfGT5mmnslhl41nk_EV_8OUdL8wMXunC2KERdnsy5XYk4aw3LlvxZDIvjxO9PEblPsoap-WErdi9GVyAv-NJ6eJQy3S7FRSkvzQYBsLnCKm5wu0kjdQBVUCFJ7wfiZ9ayY7pH7K10qN2Utvt-qsCLUy0cJ0StuP_rquefp7_XhUw3A8IIA8P6DjfZIbpwrVjOeVWoI_ZKIwfxShghOAKBDLyQuC2PhozsqZ7HvGEeAPm06YPMWQVbE9_LBn2j_Ul_VBUWc9KfBNOzk_BMQHyF2NUlwMtqMUEcwK_hpjEeo62O_aFT8EDkgcQ",
            "alg": "RS256"
        },
        {
            "kty": "RSA",
            "use": "sig",
            "kid": "LS-EQOr-3BkalkkUVh8q7Q",
            "e": "AQAB",
            "n": "08BLLaTz4JrTYmE4bZ9c7oKVrZKLy3KfGT5mmnslhl41nk_EV_8OUdL8wMXunC2KERdnsy5XYk4aw3LlvxZDIvjxO9PEblPsoap-WErdi9GVyAv-NJ6eJQy3S7FRSkvzQYBsLnCKm5wu0kjdQBVUCFJ7wfiZ9ayY7pH7K10qN2Utvt-qsCLUy0cJ0StuP_rquefp7_XhUw3A8IIA8P6DjfZIbpwrVjOeVWoI_ZKIwfxShghOAKBDLyQuC2PhozsqZ7HvGEeAPm06YPMWQVbE9_LBn2j_Ul_VBUWc9KfBNOzk_BMQHyF2NUlwMtqMUEcwK_hpjEeo62O_aFT8EDkgcQ",
            "alg": "RS256"
        }
    ]
}

原始碼決議

介面地址都在Constants.cs這個檔案,ProtocalRoutePaths這個類里面定義的,現在知道為什么介面地址是.well-known/openid-configuration這樣奇怪的一個路由了,這是oidc協議定的(對,都是產品的鍋),

image

oidc服務配置資訊介面 - DiscoveryEndpoint

代碼很長,但是邏輯很簡單,就是組裝協議規定的所有地址和資訊,
需要注意的支持的claims、支持的scope等資訊是遍歷所有IdentityResource、ApiResource動態獲取的,
基本上每個介面都可以配置是否顯示在元資料檔案中,

public async Task<IEndpointResult> ProcessAsync(HttpContext context)
{
    _logger.LogTrace("Processing discovery request.");

    // validate HTTP
    if (!HttpMethods.IsGet(context.Request.Method))
    {
        _logger.LogWarning("Discovery endpoint only supports GET requests");
        return new StatusCodeResult(HttpStatusCode.MethodNotAllowed);
    }

    _logger.LogDebug("Start discovery request");

    if (!_options.Endpoints.EnableDiscoveryEndpoint)
    {
        _logger.LogInformation("Discovery endpoint disabled. 404.");
        return new StatusCodeResult(HttpStatusCode.NotFound);
    }

    var baseUrl = context.GetIdentityServerBaseUrl().EnsureTrailingSlash();
    var issuerUri = context.GetIdentityServerIssuerUri();

    // generate response
    _logger.LogTrace("Calling into discovery response generator: {type}", _responseGenerator.GetType().FullName);
    var response = await _responseGenerator.CreateDiscoveryDocumentAsync(baseUrl, issuerUri);

    return new DiscoveryDocumentResult(response, _options.Discovery.ResponseCacheInterval);
}

/// <summary>
/// Creates the discovery document.
/// </summary>
/// <param name="baseUrl">The base URL.</param>
/// <param name="issuerUri">The issuer URI.</param>
public virtual async Task<Dictionary<string, object>> CreateDiscoveryDocumentAsync(string baseUrl, string issuerUri)
{
    var entries = new Dictionary<string, object>
    {
        { OidcConstants.Discovery.Issuer, issuerUri }
    };

    // jwks
    if (Options.Discovery.ShowKeySet)
    {
        if ((await Keys.GetValidationKeysAsync()).Any())
        {
            entries.Add(OidcConstants.Discovery.JwksUri, baseUrl + Constants.ProtocolRoutePaths.DiscoveryWebKeys);
        }
    }

    // endpoints
    if (Options.Discovery.ShowEndpoints)
    {
        if (Options.Endpoints.EnableAuthorizeEndpoint)
        {
            entries.Add(OidcConstants.Discovery.AuthorizationEndpoint, baseUrl + Constants.ProtocolRoutePaths.Authorize);
        }

        if (Options.Endpoints.EnableTokenEndpoint)
        {
            entries.Add(OidcConstants.Discovery.TokenEndpoint, baseUrl + Constants.ProtocolRoutePaths.Token);
        }

        if (Options.Endpoints.EnableUserInfoEndpoint)
        {
            entries.Add(OidcConstants.Discovery.UserInfoEndpoint, baseUrl + Constants.ProtocolRoutePaths.UserInfo);
        }

        if (Options.Endpoints.EnableEndSessionEndpoint)
        {
            entries.Add(OidcConstants.Discovery.EndSessionEndpoint, baseUrl + Constants.ProtocolRoutePaths.EndSession);
        }

        if (Options.Endpoints.EnableCheckSessionEndpoint)
        {
            entries.Add(OidcConstants.Discovery.CheckSessionIframe, baseUrl + Constants.ProtocolRoutePaths.CheckSession);
        }

        if (Options.Endpoints.EnableTokenRevocationEndpoint)
        {
            entries.Add(OidcConstants.Discovery.RevocationEndpoint, baseUrl + Constants.ProtocolRoutePaths.Revocation);
        }

        if (Options.Endpoints.EnableIntrospectionEndpoint)
        {
            entries.Add(OidcConstants.Discovery.IntrospectionEndpoint, baseUrl + Constants.ProtocolRoutePaths.Introspection);
        }

        if (Options.Endpoints.EnableDeviceAuthorizationEndpoint)
        {
            entries.Add(OidcConstants.Discovery.DeviceAuthorizationEndpoint, baseUrl + Constants.ProtocolRoutePaths.DeviceAuthorization);
        }

        if (Options.MutualTls.Enabled)
        {
            var mtlsEndpoints = new Dictionary<string, string>();

            if (Options.Endpoints.EnableTokenEndpoint)
            {
                mtlsEndpoints.Add(OidcConstants.Discovery.TokenEndpoint, baseUrl + Constants.ProtocolRoutePaths.MtlsToken);
            }
            if (Options.Endpoints.EnableTokenRevocationEndpoint)
            {
                mtlsEndpoints.Add(OidcConstants.Discovery.RevocationEndpoint, baseUrl + Constants.ProtocolRoutePaths.MtlsRevocation);
            }
            if (Options.Endpoints.EnableIntrospectionEndpoint)
            {
                mtlsEndpoints.Add(OidcConstants.Discovery.IntrospectionEndpoint, baseUrl + Constants.ProtocolRoutePaths.MtlsIntrospection);
            }
            if (Options.Endpoints.EnableDeviceAuthorizationEndpoint)
            {
                mtlsEndpoints.Add(OidcConstants.Discovery.DeviceAuthorizationEndpoint, baseUrl + Constants.ProtocolRoutePaths.MtlsDeviceAuthorization);
            }

            if (mtlsEndpoints.Any())
            {
                entries.Add(OidcConstants.Discovery.MtlsEndpointAliases, mtlsEndpoints);
            }
        }
    }

    // logout
    if (Options.Endpoints.EnableEndSessionEndpoint)
    {
        entries.Add(OidcConstants.Discovery.FrontChannelLogoutSupported, true);
        entries.Add(OidcConstants.Discovery.FrontChannelLogoutSessionSupported, true);
        entries.Add(OidcConstants.Discovery.BackChannelLogoutSupported, true);
        entries.Add(OidcConstants.Discovery.BackChannelLogoutSessionSupported, true);
    }

    // scopes and claims
    if (Options.Discovery.ShowIdentityScopes ||
        Options.Discovery.ShowApiScopes ||
        Options.Discovery.ShowClaims)
    {
        var resources = await ResourceStore.GetAllEnabledResourcesAsync();
        var scopes = new List<string>();

        // scopes
        if (Options.Discovery.ShowIdentityScopes)
        {
            scopes.AddRange(resources.IdentityResources.Where(x => x.ShowInDiscoveryDocument).Select(x => x.Name));
        }

        if (Options.Discovery.ShowApiScopes)
        {
            var apiScopes = from api in resources.ApiResources
                            from scope in api.Scopes
                            where scope.ShowInDiscoveryDocument
                            select scope.Name;

            scopes.AddRange(apiScopes);
            scopes.Add(IdentityServerConstants.StandardScopes.OfflineAccess);
        }

        if (scopes.Any())
        {
            entries.Add(OidcConstants.Discovery.ScopesSupported, scopes.ToArray());
        }

        // claims
        if (Options.Discovery.ShowClaims)
        {
            var claims = new List<string>();

            // add non-hidden identity scopes related claims
            claims.AddRange(resources.IdentityResources.Where(x => x.ShowInDiscoveryDocument).SelectMany(x => x.UserClaims));

            // add non-hidden api scopes related claims
            foreach (var resource in resources.ApiResources)
            {
                claims.AddRange(resource.UserClaims);

                foreach (var scope in resource.Scopes)
                {
                    if (scope.ShowInDiscoveryDocument)
                    {
                        claims.AddRange(scope.UserClaims);
                    }
                }
            }

            entries.Add(OidcConstants.Discovery.ClaimsSupported, claims.Distinct().ToArray());
        }
    }

    // grant types
    if (Options.Discovery.ShowGrantTypes)
    {
        var standardGrantTypes = new List<string>
        {
            OidcConstants.GrantTypes.AuthorizationCode,
            OidcConstants.GrantTypes.ClientCredentials,
            OidcConstants.GrantTypes.RefreshToken,
            OidcConstants.GrantTypes.Implicit
        };

        if (!(ResourceOwnerValidator is NotSupportedResourceOwnerPasswordValidator))
        {
            standardGrantTypes.Add(OidcConstants.GrantTypes.Password);
        }

        if (Options.Endpoints.EnableDeviceAuthorizationEndpoint)
        {
            standardGrantTypes.Add(OidcConstants.GrantTypes.DeviceCode);
        }

        var showGrantTypes = new List<string>(standardGrantTypes);

        if (Options.Discovery.ShowExtensionGrantTypes)
        {
            showGrantTypes.AddRange(ExtensionGrants.GetAvailableGrantTypes());
        }

        entries.Add(OidcConstants.Discovery.GrantTypesSupported, showGrantTypes.ToArray());
    }

    // response types
    if (Options.Discovery.ShowResponseTypes)
    {
        entries.Add(OidcConstants.Discovery.ResponseTypesSupported, Constants.SupportedResponseTypes.ToArray());
    }

    // response modes
    if (Options.Discovery.ShowResponseModes)
    {
        entries.Add(OidcConstants.Discovery.ResponseModesSupported, Constants.SupportedResponseModes.ToArray());
    }

    // misc
    if (Options.Discovery.ShowTokenEndpointAuthenticationMethods)
    {
        var types = SecretParsers.GetAvailableAuthenticationMethods().ToList();
        if (Options.MutualTls.Enabled)
        {
            types.Add(OidcConstants.EndpointAuthenticationMethods.TlsClientAuth);
            types.Add(OidcConstants.EndpointAuthenticationMethods.SelfSignedTlsClientAuth);
        }

        entries.Add(OidcConstants.Discovery.TokenEndpointAuthenticationMethodsSupported, types);
    }
    
    var signingCredentials = await Keys.GetSigningCredentialsAsync();
    if (signingCredentials != null)
    {
        var algorithm = signingCredentials.Algorithm;
        entries.Add(OidcConstants.Discovery.IdTokenSigningAlgorithmsSupported, new[] { algorithm });
    }

    entries.Add(OidcConstants.Discovery.SubjectTypesSupported, new[] { "public" });
    entries.Add(OidcConstants.Discovery.CodeChallengeMethodsSupported, new[] { OidcConstants.CodeChallengeMethods.Plain, OidcConstants.CodeChallengeMethods.Sha256 });

    if (Options.Endpoints.EnableAuthorizeEndpoint)
    {
        entries.Add(OidcConstants.Discovery.RequestParameterSupported, true);

        if (Options.Endpoints.EnableJwtRequestUri)
        {
            entries.Add(OidcConstants.Discovery.RequestUriParameterSupported, true);
        }
    }

    if (Options.MutualTls.Enabled)
    {
        entries.Add(OidcConstants.Discovery.TlsClientCertificateBoundAccessTokens, true);
    }

    // custom entries
    if (!Options.Discovery.CustomEntries.IsNullOrEmpty())
    {
        foreach (var customEntry in Options.Discovery.CustomEntries)
        {
            if (entries.ContainsKey(customEntry.Key))
            {
                Logger.LogError("Discovery custom entry {key} cannot be added, because it already exists.", customEntry.Key);
            }
            else
            {
                if (customEntry.Value is string customValueString)
                {
                    if (customValueString.StartsWith("~/") && Options.Discovery.ExpandRelativePathsInCustomEntries)
                    {
                        entries.Add(customEntry.Key, baseUrl + customValueString.Substring(2));
                        continue;
                    }
                }

                entries.Add(customEntry.Key, customEntry.Value);
            }
        }
    }

    return entries;
}

然后是jwks描述資訊的代碼,關于加密的資訊也是根據配置的SecuritKey去動態回傳的,

public virtual async Task<IEnumerable<Models.JsonWebKey>> CreateJwkDocumentAsync()
    {
        var webKeys = new List<Models.JsonWebKey>();
        
        foreach (var key in await Keys.GetValidationKeysAsync())
        {
            if (key.Key is X509SecurityKey x509Key)
            {
                var cert64 = Convert.ToBase64String(x509Key.Certificate.RawData);
                var thumbprint = Base64Url.Encode(x509Key.Certificate.GetCertHash());

                if (x509Key.PublicKey is RSA rsa)
                {
                    var parameters = rsa.ExportParameters(false);
                    var exponent = Base64Url.Encode(parameters.Exponent);
                    var modulus = Base64Url.Encode(parameters.Modulus);

                    var rsaJsonWebKey = new Models.JsonWebKey
                    {
                        kty = "RSA",
                        use = "sig",
                        kid = x509Key.KeyId,
                        x5t = thumbprint,
                        e = exponent,
                        n = modulus,
                        x5c = new[] { cert64 },
                        alg = key.SigningAlgorithm
                    };
                    webKeys.Add(rsaJsonWebKey);
                }
                else if (x509Key.PublicKey is ECDsa ecdsa)
                {
                    var parameters = ecdsa.ExportParameters(false);
                    var x = Base64Url.Encode(parameters.Q.X);
                    var y = Base64Url.Encode(parameters.Q.Y);

                    var ecdsaJsonWebKey = new Models.JsonWebKey
                    {
                        kty = "EC",
                        use = "sig",
                        kid = x509Key.KeyId,
                        x5t = thumbprint,
                        x = x,
                        y = y,
                        crv = CryptoHelper.GetCrvValueFromCurve(parameters.Curve),
                        x5c = new[] { cert64 },
                        alg = key.SigningAlgorithm
                    };
                    webKeys.Add(ecdsaJsonWebKey);
                }
                else
                {
                    throw new InvalidOperationException($"key type: {x509Key.PublicKey.GetType().Name} not supported.");
                }
            }
            else if (key.Key is RsaSecurityKey rsaKey)
            {
                var parameters = rsaKey.Rsa?.ExportParameters(false) ?? rsaKey.Parameters;
                var exponent = Base64Url.Encode(parameters.Exponent);
                var modulus = Base64Url.Encode(parameters.Modulus);

                var webKey = new Models.JsonWebKey
                {
                    kty = "RSA",
                    use = "sig",
                    kid = rsaKey.KeyId,
                    e = exponent,
                    n = modulus,
                    alg = key.SigningAlgorithm
                };

                webKeys.Add(webKey);
            }
            else if (key.Key is ECDsaSecurityKey ecdsaKey)
            {
                var parameters = ecdsaKey.ECDsa.ExportParameters(false);
                var x = Base64Url.Encode(parameters.Q.X);
                var y = Base64Url.Encode(parameters.Q.Y);

                var ecdsaJsonWebKey = new Models.JsonWebKey
                {
                    kty = "EC",
                    use = "sig",
                    kid = ecdsaKey.KeyId,
                    x = x,
                    y = y,
                    crv = CryptoHelper.GetCrvValueFromCurve(parameters.Curve),
                    alg = key.SigningAlgorithm
                };
                webKeys.Add(ecdsaJsonWebKey);
            }
            else if (key.Key is JsonWebKey jsonWebKey)
            {
                var webKey = new Models.JsonWebKey
                {
                    kty = jsonWebKey.Kty,
                    use = jsonWebKey.Use ?? "sig",
                    kid = jsonWebKey.Kid,
                    x5t = jsonWebKey.X5t,
                    e = jsonWebKey.E,
                    n = jsonWebKey.N,
                    x5c = jsonWebKey.X5c?.Count == 0 ? null : jsonWebKey.X5c.ToArray(),
                    alg = jsonWebKey.Alg,

                    x = jsonWebKey.X,
                    y = jsonWebKey.Y
                };

                webKeys.Add(webKey);
            }
        }

        return webKeys;
    }

結語

這一節還是比較好理解的,總而言之就是oidc協議規定了,需要提供GET介面,回傳所有介面的地址,以及相關配置資訊,idsv4的實作方式就是介面地址根據協議規定的去拼接,其他配置項資訊根據開發的配置去動態獲取,然后以協議約定的JSON格式回傳,

轉載請註明出處,本文鏈接:https://www.uj5u.com/net/52870.html

標籤:.NET Core

上一篇:IdentityServer4原始碼決議_1_專案結構

下一篇:.netcore2.1 使用middleware對api請求頭進行驗證

標籤雲
其他(157675) Python(38076) JavaScript(25376) Java(17977) C(15215) 區塊鏈(8255) C#(7972) AI(7469) 爪哇(7425) MySQL(7132) html(6777) 基礎類(6313) sql(6102) 熊猫(6058) PHP(5869) 数组(5741) R(5409) Linux(5327) 反应(5209) 腳本語言(PerlPython)(5129) 非技術區(4971) Android(4554) 数据框(4311) css(4259) 节点.js(4032) C語言(3288) json(3245) 列表(3129) 扑(3119) C++語言(3117) 安卓(2998) 打字稿(2995) VBA(2789) Java相關(2746) 疑難問題(2699) 细绳(2522) 單片機工控(2479) iOS(2429) ASP.NET(2402) MongoDB(2323) 麻木的(2285) 正则表达式(2254) 字典(2211) 循环(2198) 迅速(2185) 擅长(2169) 镖(2155) 功能(1967) .NET技术(1958) Web開發(1951) python-3.x(1918) HtmlCss(1915) 弹簧靴(1913) C++(1909) xml(1889) PostgreSQL(1872) .NETCore(1853) 谷歌表格(1846) Unity3D(1843) for循环(1842)

熱門瀏覽
  • WebAPI簡介

    Web體系結構: 有三個核心:資源(resource),URL(統一資源識別符號)和表示 他們的關系是這樣的:一個資源由一個URL進行標識,HTTP客戶端使用URL定位資源,表示是從資源回傳資料,媒體型別是資源回傳的資料格式。 接下來我們說下HTTP. HTTP協議的系統是一種無狀態的方式,使用請求/ ......

    uj5u.com 2020-09-09 22:07:47 more
  • asp.net core 3.1 入口:Program.cs中的Main函式

    本文分析Program.cs 中Main()函式中代碼的運行順序分析asp.net core程式的啟動,重點不是剖析原始碼,而是理清程式開始時執行的順序。到呼叫了哪些實體,哪些法方。asp.net core 3.1 的程式入口在專案Program.cs檔案里,如下。ususing System; us ......

    uj5u.com 2020-09-09 22:07:49 more
  • asp.net網站作為websocket服務端的應用該如何寫

    最近被websocket的一個問題困擾了很久,有一個需求是在web網站中搭建websocket服務。客戶端通過網頁與服務器建立連接,然后服務器根據ip給客戶端網頁發送資訊。 其實,這個需求并不難,只是剛開始對websocket的內容不太了解。上網搜索了一下,有通過asp.net core 實作的、有 ......

    uj5u.com 2020-09-09 22:08:02 more
  • ASP.NET 開源匯入匯出庫Magicodes.IE Docker中使用

    Magicodes.IE在Docker中使用 更新歷史 2019.02.13 【Nuget】版本更新到2.0.2 【匯入】修復單列匯入的Bug,單元測驗“OneColumnImporter_Test”。問題見(https://github.com/dotnetcore/Magicodes.IE/is ......

    uj5u.com 2020-09-09 22:08:05 more
  • 在webform中使用ajax

    如果你用過Asp.net webform, 說明你也算是.NET 開發的老兵了。WEBform應該是2011 2013左右,當時還用visual studio 2005、 visual studio 2008。后來基本都用的是MVC。 如果是新開發的專案,估計沒人會用webform技術。但是有些舊版 ......

    uj5u.com 2020-09-09 22:08:50 more
  • iis添加asp.net網站,訪問提示:由于擴展配置問題而無法提供您請求的

    今天在iis服務器配置asp.net網站,遇到一個問題,記錄一下: 問題:由于擴展配置問題而無法提供您請求的頁面。如果該頁面是腳本,請添加處理程式。如果應下載檔案,請添加 MIME 映射。 WindowServer2012服務器,添加角色安裝完.netframework和iis之后,運行aspx頁面 ......

    uj5u.com 2020-09-09 22:10:00 more
  • WebAPI-處理架構

    帶著問題去思考,大家好! 問題1:HTTP請求和回傳相應的HTTP回應資訊之間發生了什么? 1:首先是最底層,托管層,位于WebAPI和底層HTTP堆疊之間 2:其次是 訊息處理程式管道層,這里比如日志和快取。OWIN的參考是將訊息處理程式管道的一些功能下移到堆疊下端的OWIN中間件了。 3:控制器處理 ......

    uj5u.com 2020-09-09 22:11:13 more
  • 微信門戶開發框架-使用指導說明書

    微信門戶應用管理系統,采用基于 MVC + Bootstrap + Ajax + Enterprise Library的技術路線,界面層采用Boostrap + Metronic組合的前端框架,資料訪問層支持Oracle、SQLServer、MySQL、PostgreSQL等資料庫。框架以MVC5,... ......

    uj5u.com 2020-09-09 22:15:18 more
  • WebAPI-HTTP編程模型

    帶著問題去思考,大家好!它是什么?它包含什么?它能干什么? 訊息 HTTP編程模型的核心就是訊息抽象,表示為:HttPRequestMessage,HttpResponseMessage.用于客戶端和服務端之間交換請求和回應訊息。 HttpMethod類包含了一組靜態屬性: private stat ......

    uj5u.com 2020-09-09 22:15:23 more
  • 部署WebApi隨筆

    一、跨域 NuGet參考Microsoft.AspNet.WebApi.Cors WebApiConfig.cs中配置: // Web API 配置和服務 config.EnableCors(new EnableCorsAttribute("*", "*", "*")); 二、清除默認回傳XML格式 ......

    uj5u.com 2020-09-09 22:15:48 more
最新发布
  • C#多執行緒學習(二) 如何操縱一個執行緒

    <a href="https://www.cnblogs.com/x-zhi/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/2943582/20220801082530.png" alt="" /></...

    uj5u.com 2023-04-19 09:17:20 more
  • C#多執行緒學習(二) 如何操縱一個執行緒

    C#多執行緒學習(二) 如何操縱一個執行緒 執行緒學習第一篇:C#多執行緒學習(一) 多執行緒的相關概念 下面我們就動手來創建一個執行緒,使用Thread類創建執行緒時,只需提供執行緒入口即可。(執行緒入口使程式知道該讓這個執行緒干什么事) 在C#中,執行緒入口是通過ThreadStart代理(delegate)來提供的 ......

    uj5u.com 2023-04-19 09:16:49 more
  • 記一次 .NET某醫療器械清洗系統 卡死分析

    <a href="https://www.cnblogs.com/huangxincheng/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/214741/20200614104537.png" alt="" /&g...

    uj5u.com 2023-04-18 08:39:04 more
  • 記一次 .NET某醫療器械清洗系統 卡死分析

    一:背景 1. 講故事 前段時間協助訓練營里的一位朋友分析了一個程式卡死的問題,回過頭來看這個案例比較經典,這篇稍微整理一下供后來者少踩坑吧。 二:WinDbg 分析 1. 為什么會卡死 因為是表單程式,理所當然就是看主執行緒此時正在做什么? 可以用 ~0s ; k 看一下便知。 0:000> k # ......

    uj5u.com 2023-04-18 08:33:10 more
  • SignalR, No Connection with that ID,IIS

    <a href="https://www.cnblogs.com/smartstar/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/u36196.jpg" alt="" /></a>...

    uj5u.com 2023-03-30 17:21:52 more
  • 一次對pool的誤用導致的.net頻繁gc的診斷分析

    <a href="https://www.cnblogs.com/dotnet-diagnostic/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/3115652/20230225090434.png" alt=""...

    uj5u.com 2023-03-28 10:15:33 more
  • 一次對pool的誤用導致的.net頻繁gc的診斷分析

    <a href="https://www.cnblogs.com/dotnet-diagnostic/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/3115652/20230225090434.png" alt=""...

    uj5u.com 2023-03-28 10:13:31 more
  • C#遍歷指定檔案夾中所有檔案的3種方法

    <a href="https://www.cnblogs.com/xbhp/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/957602/20230310105611.png" alt="" /></a&...

    uj5u.com 2023-03-27 14:46:55 more
  • C#/VB.NET:如何將PDF轉為PDF/A

    <a href="https://www.cnblogs.com/Carina-baby/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/2859233/20220427162558.png" alt="" />...

    uj5u.com 2023-03-27 14:46:35 more
  • 武裝你的WEBAPI-OData聚合查詢

    <a href="https://www.cnblogs.com/podolski/" target="_blank"><img width="48" height="48" class="pfs" src="https://pic.cnblogs.com/face/616093/20140323000327.png" alt="" /><...

    uj5u.com 2023-03-27 14:46:16 more