主頁 > .NET開發 > 無法使用ssh克隆github存盤庫

無法使用ssh克隆github存盤庫

2022-05-08 21:09:02 .NET開發

我正在使用 Windows 10，帶有 Cygwin（用于 unix 命令）和來自 scoop 的（git，OpenSSH）。

錯誤：

? git clone [email protected]:tshrpl/avis.git
Cloning into 'avis'..
[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

SSH 除錯輸出：

? ssh -Tvvv [email protected]
OpenSSH_for_Windows_8.9p1, LibreSSL 3.4.3
debug3: Failed to open file:C:/Users/hitus/.ssh/config error:2
debug3: Failed to open file:C:/ProgramData/ssh/ssh_config error:2
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 'C:\\Users\\hitus/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 'C:\\Users\\hitus/.ssh/known_hosts2'
debug2: resolving "github.com" port 22
debug3: resolve_host: lookup github.com:22
debug3: ssh_connect_direct: entering
debug1: Connecting to github.com [13.234.176.102] port 22.
debug1: Connection established.
debug3: Failed to open file:C:/Users/hitus/.ssh/id_rsa error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_rsa.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_rsa error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_rsa type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_rsa-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_rsa-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_rsa-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_rsa-cert type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ecdsa error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ecdsa type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ecdsa-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ecdsa-cert type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa_sk error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa_sk.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ecdsa_sk error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ecdsa_sk type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa_sk-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ecdsa_sk-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ecdsa_sk-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file C:\\Users\\hitus/.ssh/id_ed25519 type 3
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ed25519-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ed25519-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ed25519-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ed25519-cert type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ed25519_sk error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ed25519_sk.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ed25519_sk error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ed25519_sk type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ed25519_sk-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_ed25519_sk-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_ed25519_sk-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_ed25519_sk-cert type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_xmss error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_xmss.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_xmss error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_xmss type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_xmss-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_xmss-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_xmss-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_xmss-cert type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_dsa error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_dsa.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_dsa error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_dsa type -1
debug3: Failed to open file:C:/Users/hitus/.ssh/id_dsa-cert error:2
debug3: Failed to open file:C:/Users/hitus/.ssh/id_dsa-cert.pub error:2
debug3: failed to open file:C:/Users/hitus/.ssh/id_dsa-cert error:2
debug1: identity file C:\\Users\\hitus/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_for_Windows_8.9
debug1: Remote protocol version 2.0, remote software version babeld-65a6644c
debug1: compat_banner: no match: babeld-65a6644c
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to github.com:22 as 'git'
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\hitus/.ssh/known_hosts:4
debug3: load_hostkeys_file: loaded 1 keys from github.com
debug3: Failed to open file:C:/Users/hitus/.ssh/known_hosts2 error:2
debug1: load_hostkeys: fopen C:\\Users\\hitus/.ssh/known_hosts2: No such file or directory
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],ecdsa-sha2-nistp256
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512
,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c
debug2: host key algorithms: [email protected],ecdsa-sha2-nistp256,[email protected],[email protected],ecdsa-sha2-nistp521-cert-v01@o
penssh.com,[email protected],[email protected],[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp384,ecd
sa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected]
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected]
,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected]
,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected],zlib
debug2: compression stoc: none,[email protected],zlib
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256
debug2: host key algorithms: ssh-ed25519,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: [email protected],[email protected],[email protected],aes256-ctr,aes192-ctr,aes128-ctr
debug2: ciphers stoc: [email protected],[email protected],[email protected],aes256-ctr,aes192-ctr,aes128-ctr
debug2: MACs ctos: [email protected],[email protected],hmac-sha2-512,hmac-sha2-256
debug2: MACs stoc: [email protected],[email protected],hmac-sha2-512,hmac-sha2-256
debug2: compression ctos: none
debug2: compression stoc: none
debug2: languages ctos:
debug2: languages stoc:
debug2: first_kex_follows 0
debug2: reserved 0
debug1: kex: algorithm: curve25519-sha256
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none
debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none
debug3: send packet: type 30
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM
debug3: record_hostkey: found key type ECDSA in file C:\\Users\\hitus/.ssh/known_hosts:4
debug3: load_hostkeys_file: loaded 1 keys from github.com
debug3: Failed to open file:C:/Users/hitus/.ssh/known_hosts2 error:2
debug1: load_hostkeys: fopen C:\\Users\\hitus/.ssh/known_hosts2: No such file or directory
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts error:2
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts: No such file or directory
debug3: Failed to open file:C:/ProgramData/ssh/ssh_known_hosts2 error:2
debug1: load_hostkeys: fopen __PROGRAMDATA__\\ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'github.com' is known and matches the ECDSA host key.
debug1: Found key in C:\\Users\\hitus/.ssh/known_hosts:4
debug3: send packet: type 21
debug2: ssh_set_newkeys: mode 1
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: ssh_set_newkeys: mode 0
debug1: rekey in after 134217728 blocks
debug2: get_agent_identities: ssh_agent_bind_hostkey: communication with agent failed
debug3: write ERROR from cb(2):232, io:00000219C68446F0
debug1: get_agent_identities: ssh_fetch_identitylist: communication with agent failed
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_rsa
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_ecdsa
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_ecdsa_sk
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_ed25519 ED25519 SHA256:JYyA/L72AmyrIMX/S4w6aIS 4HTVQkDUWlhARj  5fI
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_ed25519_sk
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_xmss
debug1: Will attempt key: C:\\Users\\hitus/.ssh/id_dsa
debug2: pubkey_prepare: done
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<[email protected],[email protected],[email protected],ecdsa-sha2-nistp256-cert-v01@opens
sh.com,[email protected],[email protected],[email protected],[email protected],[email protected],sk-ssh-ed2
[email protected],[email protected],ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey
debug3: start over, passed a different list publickey
debug3: preferred publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: C:\\Users\\hitus/.ssh/id_rsa
debug3: no such identity: C:\\Users\\hitus/.ssh/id_rsa: No such file or directory
debug1: Trying private key: C:\\Users\\hitus/.ssh/id_ecdsa
debug3: no such identity: C:\\Users\\hitus/.ssh/id_ecdsa: No such file or directory
debug1: Trying private key: C:\\Users\\hitus/.ssh/id_ecdsa_sk
debug3: no such identity: C:\\Users\\hitus/.ssh/id_ecdsa_sk: No such file or directory
debug1: Offering public key: C:\\Users\\hitus/.ssh/id_ed25519 ED25519 SHA256:JYyA/L72AmyrIMX/S4w6aIS 4HTVQkDUWlhARj  5fI
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: C:\\Users\\hitus/.ssh/id_ed25519 ED25519 SHA256:JYyA/L72AmyrIMX/S4w6aIS 4HTVQkDUWlhARj  5fI
debug3: sign_and_send_pubkey: using publickey with ED25519 SHA256:JYyA/L72AmyrIMX/S4w6aIS 4HTVQkDUWlhARj  5fI
debug3: sign_and_send_pubkey: signing using ssh-ed25519 SHA256:JYyA/L72AmyrIMX/S4w6aIS 4HTVQkDUWlhARj  5fI
debug3: send packet: type 50
debug3: receive packet: type 52
Authenticated to github.com ([13.234.176.102]:22) using "publickey".
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug3: send packet: type 90
debug1: Entering interactive session.
debug1: pledge: filesystem
debug3: receive packet: type 80
debug1: client_input_global_request: rtype [email protected] want_reply 0
debug3: client_input_hostkeys: received RSA key SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug3: client_input_hostkeys: received ECDSA key SHA256:p2QAMXNIC1TJYWeIOttrVc98/R1BUFWu3/LiyKgUfQM
debug3: client_input_hostkeys: received ED25519 key SHA256: DiY3wvvV6TuJJhbpZisF/zLDA0zPMSvHdkr4UvCOqU
debug1: client_input_hostkeys: searching C:\\Users\\hitus/.ssh/known_hosts for github.com / (none)
debug3: hostkeys_foreach: reading file "C:\\Users\\hitus/.ssh/known_hosts"
debug3: hostkeys_find: found ssh-ed25519 key under different name/addr at C:\\Users\\hitus/.ssh/known_hosts:1
debug3: hostkeys_find: found ssh-rsa key under different name/addr at C:\\Users\\hitus/.ssh/known_hosts:2
debug3: hostkeys_find: found ecdsa-sha2-nistp256 key under different name/addr at C:\\Users\\hitus/.ssh/known_hosts:3
debug3: hostkeys_find: found ecdsa-sha2-nistp256 key at C:\\Users\\hitus/.ssh/known_hosts:4
debug3: hostkeys_find: found ecdsa-sha2-nistp256 key under different name/addr at C:\\Users\\hitus/.ssh/known_hosts:5
debug1: client_input_hostkeys: searching C:\\Users\\hitus/.ssh/known_hosts2 for github.com / (none)
debug3: Failed to open file:C:/Users/hitus/.ssh/known_hosts2 error:2
debug1: client_input_hostkeys: hostkeys file C:\\Users\\hitus/.ssh/known_hosts2 does not exist
debug3: client_input_hostkeys: 3 server keys: 2 new, 18446744073709551615 retained, 2 incomplete match. 0 to remove
debug1: client_input_hostkeys: host key found matching a different name/address, skipping UserKnownHostsFile update
debug3: receive packet: type 91
debug2: channel_input_open_confirmation: channel 0: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request shell confirm 1
debug3: send packet: type 98
debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 32000 rmax 35000
debug3: receive packet: type 99
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
debug2: channel 0: rcvd ext data 88
debug3: receive packet: type 98
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug3: receive packet: type 96
debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug3: receive packet: type 97
debug2: channel 0: rcvd close
debug2: chan_shutdown_read: channel 0: (i0 o1 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: obuf_empty delayed efd 6/(88)
Hi tshrpl! You've successfully authenticated, but GitHub does not provide shell access.
debug2: channel 0: written 88 to efd 6
debug3: channel 0: will not send data after close
debug2: channel 0: obuf empty
debug2: chan_shutdown_write: channel 0: (i3 o1 sock -1 wfd 5 efd 6 [write])
debug2: channel 0: output drain -> closed
debug2: channel 0: almost dead
debug2: channel 0: gc: notify user
debug2: channel 0: gc: user detached
debug2: channel 0: send close
debug3: send packet: type 97
debug2: channel 0: is dead
debug2: channel 0: garbage collecting
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
  #0 client-session (t4 r43 i3/0 o3/0 e[write]/0 fd -1/-1/6 sock -1 cc -1 io 0x00/0x08)

debug3: send packet: type 1
Transferred: sent 2072, received 2376 bytes, in 0.6 seconds
Bytes per second: sent 3759.6, received 4311.2
debug1: Exit status 1

uj5u.com熱心網友回復：

當我在 ~/.ssh 檔案夾中運行 dir 時，我只看到一對密鑰

然后檢查公鑰是否已注冊到您的GitHub SSH 設定。

您應該在那里看到一個帶有指紋的鍵。

將其指紋與您的指紋進行比較（假設您的密鑰名為id_rsa.pub）：

ssh-keygen -l -f /path/to/keys/id_rsa.pub

考慮到您確實有一條歡迎訊息，這應該是相同的：

Hi tshrpl! You've successfully authenticated, but GitHub does not provide shell access.

我剛剛測驗過git clone [email protected]:tshrpl/avis：它確實有效。

確保您沒有在（根）會話中鍵入您的第一個git clone命令。sudo

OP tshrpl在評論中報告：

手動終止ssh-agent行程并重新啟動后，通過 ssh 克隆就可以了！！

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

標籤：视窗 混帐 github SSH

上一篇：wincmd中的批處理腳本回圈

下一篇：在服務器串列中查找用戶PowerShell

標籤雲
其他(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

Copyright © 2010-2020 有解無憂