fix: MD034/no-bare-urls (#18470)
Bare URL used Co-authored-by: Maira Wenzel <mairaw@microsoft.com>
This commit is contained in:
Nick Schonning
GitHub
Родитель
1615b57465
Коммит
4e320efb46
|
|
@ -8,9 +8,9 @@ see the [LICENSE](LICENSE) file, and grant you a license to any code in the repo
|
|||
Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation
|
||||
may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries.
|
||||
The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks.
|
||||
Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653.
|
||||
Microsoft's general trademark guidelines can be found at <https://go.microsoft.com/fwlink/?LinkID=254653>.
|
||||
|
||||
Privacy information can be found at https://privacy.microsoft.com/
|
||||
Privacy information can be found at <https://privacy.microsoft.com/>
|
||||
|
||||
Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents,
|
||||
or trademarks, whether by implication, estoppel or otherwise.
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ This book is provided "as-is" and expresses the author's views and opinions. The
|
|||
|
||||
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
|
||||
|
||||
Microsoft and the trademarks listed at [https://www.microsoft.com](https://www.microsoft.com) on the "Trademarks" webpage are trademarks of the Microsoft group of companies.
|
||||
Microsoft and the trademarks listed at <https://www.microsoft.com> on the "Trademarks" webpage are trademarks of the Microsoft group of companies.
|
||||
|
||||
Mac and macOS are trademarks of Apple Inc.
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ This book is provided "as-is" and expresses the author's views and opinions. The
|
|||
|
||||
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
|
||||
|
||||
Microsoft and the trademarks listed at https://www.microsoft.com on the "Trademarks" webpage are trademarks of the Microsoft group of companies.
|
||||
Microsoft and the trademarks listed at <https://www.microsoft.com> on the "Trademarks" webpage are trademarks of the Microsoft group of companies.
|
||||
|
||||
The Docker whale logo is a registered trademark of Docker, Inc. Used by permission.
|
||||
|
||||
|
|
|
|||
|
|
@ -32,10 +32,10 @@ Using .NET Framework on Docker can improve your deployment experiences by minimi
|
|||
### Additional resources
|
||||
|
||||
- **E-book: Modernize existing .NET Framework applications with Azure and Windows Containers**
|
||||
https://aka.ms/liftandshiftwithcontainersebook
|
||||
<https://aka.ms/liftandshiftwithcontainersebook>
|
||||
|
||||
- **Sample apps: Modernization of legacy ASP.NET web apps by using Windows Containers**
|
||||
https://aka.ms/eshopmodernizing
|
||||
<https://aka.ms/eshopmodernizing>
|
||||
|
||||
>[!div class="step-by-step"]
|
||||
>[Previous](index.md)
|
||||
|
|
|
|||
|
|
@ -416,7 +416,7 @@ Be especially careful about "rolling your own" implementation of cryptography, u
|
|||
> ### References – Security
|
||||
>
|
||||
> - **Security Docs Overview**
|
||||
> https://docs.microsoft.com/aspnet/core/security/
|
||||
> <https://docs.microsoft.com/aspnet/core/security/>
|
||||
> - **Enforcing SSL in an ASP.NET Core App**
|
||||
> <https://docs.microsoft.com/aspnet/core/security/enforcing-ssl>
|
||||
> - **Introduction to Identity**
|
||||
|
|
@ -487,7 +487,7 @@ Consider ways in which your applications communicate directly with client applic
|
|||
> - **ASP.NET Core SignalR**
|
||||
> <https://github.com/dotnet/aspnetcore/tree/master/src/SignalR>
|
||||
> - **WebSocket Manager**
|
||||
> https://github.com/radu-matei/websocket-manager
|
||||
> <https://github.com/radu-matei/websocket-manager>
|
||||
|
||||
## Domain-driven design – Should you apply it?
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ This book is provided "as-is" and expresses the author's views and opinions. The
|
|||
|
||||
Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.
|
||||
|
||||
Microsoft and the trademarks listed at https://www.microsoft.com on the "Trademarks" webpage are trademarks of the Microsoft group of companies.
|
||||
Microsoft and the trademarks listed at <https://www.microsoft.com> on the "Trademarks" webpage are trademarks of the Microsoft group of companies.
|
||||
|
||||
Mac and macOS are trademarks of Apple Inc.
|
||||
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ To learn how to implement strategies for handling partial failures in the cloud,
|
|||
|
||||
- **Polly library for resilient HTTP communication**
|
||||
|
||||
https://github.com/App-vNext/Polly
|
||||
<https://github.com/App-vNext/Polly>
|
||||
|
||||
>[!div class="step-by-step"]
|
||||
>[Previous](when-to-deploy-windows-containers-to-azure-container-service-kubernetes.md)
|
||||
|
|
|
|||
|
|
@ -15,8 +15,8 @@ The following SDKs are available for .NET Core:
|
|||
|
||||
| ID | Description | Repo|
|
||||
| - | - | - |
|
||||
| `Microsoft.NET.Sdk` | The .NET Core SDK | https://github.com/dotnet/sdk |
|
||||
| `Microsoft.NET.Sdk.Web` | The .NET Core [Web SDK](/aspnet/core/razor-pages/web-sdk) | https://github.com/aspnet/websdk |
|
||||
| `Microsoft.NET.Sdk` | The .NET Core SDK | <https://github.com/dotnet/sdk> |
|
||||
| `Microsoft.NET.Sdk.Web` | The .NET Core [Web SDK](/aspnet/core/razor-pages/web-sdk) | <https://github.com/aspnet/websdk> |
|
||||
| `Microsoft.NET.Sdk.Razor` | The .NET Core [Razor SDK](/aspnet/core/razor-pages/sdk) |
|
||||
| `Microsoft.NET.Sdk.Worker` | The .NET Core Worker Service SDK |
|
||||
| `Microsoft.NET.Sdk.WindowsDesktop` | The .NET Core WinForms and WPF SDK |
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@ Enhancements were made that affect how integrated Windows authentication is hand
|
|||
## Extended Protection for Server Applications
|
||||
<xref:System.Net.HttpListener> automatically provides mechanisms for validating service bindings when performing HTTP authentication.
|
||||
|
||||
The most secure scenario is to enable extended protection for HTTPS:// prefixes. In this case, set <xref:System.Net.HttpListener.ExtendedProtectionPolicy%2A?displayProperty=nameWithType> to an <xref:System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy> with <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement> set to <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> or <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always>, and <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario> set to <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario.TransportSelected> A value of <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> puts <xref:System.Net.HttpListener> in partially hardened mode, while <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always> corresponds to fully hardened mode.
|
||||
The most secure scenario is to enable extended protection for `HTTPS://` prefixes. In this case, set <xref:System.Net.HttpListener.ExtendedProtectionPolicy%2A?displayProperty=nameWithType> to an <xref:System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy> with <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement> set to <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> or <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always>, and <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario> set to <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario.TransportSelected> A value of <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> puts <xref:System.Net.HttpListener> in partially hardened mode, while <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always> corresponds to fully hardened mode.
|
||||
|
||||
In this configuration when a request is made to the server through an outer secure channel, the outer channel is queried for a channel binding. This channel binding is passed to the authentication SSPI calls, which validate that the channel binding in the authentication blob matches. There are three possible outcomes:
|
||||
|
||||
|
|
@ -124,7 +124,7 @@ Enhancements were made that affect how integrated Windows authentication is hand
|
|||
|
||||
If an application makes its own SSPI calls to perform authentication based on blobs passed back and forth within the body of an HTTP request and wishes to support channel binding, it needs to retrieve the expected channel binding from the outer secure channel using <xref:System.Net.HttpListener> in order to pass it to native Win32 [AcceptSecurityContext](/windows/win32/api/sspi/nf-sspi-acceptsecuritycontext) function. To do this, use the <xref:System.Net.HttpListenerRequest.TransportContext%2A> property and call <xref:System.Net.TransportContext.GetChannelBinding%2A> method to retrieve the CBT. Only endpoint bindings are supported. If anything other <xref:System.Security.Authentication.ExtendedProtection.ChannelBindingKind.Endpoint> is specified, a <xref:System.NotSupportedException> will be thrown. If the underlying operating system supports channel binding, the <xref:System.Net.TransportContext.GetChannelBinding%2A> method will return a <xref:System.Security.Authentication.ExtendedProtection.ChannelBinding><xref:System.Runtime.InteropServices.SafeHandle> wrapping a pointer to a channel binding suitable for passing to [AcceptSecurityContext](/windows/win32/api/sspi/nf-sspi-acceptsecuritycontext) function as the pvBuffer member of a SecBuffer structure passed in the `pInput` parameter. The <xref:System.Security.Authentication.ExtendedProtection.ChannelBinding.Size%2A> property contains the length, in bytes, of the channel binding. If the underlying operating system does not support channel bindings, the function will return `null`.
|
||||
|
||||
Another possible scenario is to enable extended protection for HTTP:// prefixes when proxies are not used. In this case, set <xref:System.Net.HttpListener.ExtendedProtectionPolicy%2A?displayProperty=nameWithType> to an <xref:System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy> with <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement> set to <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> or <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always>, and <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario> set to <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario.TransportSelected> A value of <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> puts <xref:System.Net.HttpListener> in partially hardened mode, while <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always> corresponds to fully hardened mode.
|
||||
Another possible scenario is to enable extended protection for `HTTP://` prefixes when proxies are not used. In this case, set <xref:System.Net.HttpListener.ExtendedProtectionPolicy%2A?displayProperty=nameWithType> to an <xref:System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy> with <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement> set to <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> or <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always>, and <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario> set to <xref:System.Security.Authentication.ExtendedProtection.ProtectionScenario.TransportSelected> A value of <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.WhenSupported> puts <xref:System.Net.HttpListener> in partially hardened mode, while <xref:System.Security.Authentication.ExtendedProtection.PolicyEnforcement.Always> corresponds to fully hardened mode.
|
||||
|
||||
A default list of allowed service names is created based on the prefixes which have been registered with the <xref:System.Net.HttpListener>. This default list can be examined through the <xref:System.Net.HttpListener.DefaultServiceNames%2A> property. If this list is not comprehensive, an application can specify a custom service name collection in the constructor for the <xref:System.Security.Authentication.ExtendedProtection.ExtendedProtectionPolicy> class which will be used instead of the default service name list.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ ms.assetid: 87bee662-0a3e-4232-a421-20e7a5968321
|
|||
|
||||
<a name="Programming_Languages_compare"></a>
|
||||
## Programming Languages
|
||||
<Active Accessibility is based on the Component Object Model (COM) with support for dual interfaces, and is therefore programmable in C/C++, Microsoft Visual Basic 6.0, and scripting languages. [!INCLUDE[TLA2#tla_uiautomation](../../../includes/tla2sharptla-uiautomation-md.md)] (including the client-side provider library for standard controls) is written in managed code, and UI Automation client applications are most easily programmed using C# or Visual Basic .NET. UI Automation providers, which are interface implementations, can be written in managed code or in C/C++.
|
||||
Active Accessibility is based on the Component Object Model (COM) with support for dual interfaces, and is therefore programmable in C/C++, Microsoft Visual Basic 6.0, and scripting languages. [!INCLUDE[TLA2#tla_uiautomation](../../../includes/tla2sharptla-uiautomation-md.md)] (including the client-side provider library for standard controls) is written in managed code, and UI Automation client applications are most easily programmed using C# or Visual Basic .NET. UI Automation providers, which are interface implementations, can be written in managed code or in C/C++.
|
||||
|
||||
<a name="Support_in_Windows_Presentation_Foundation_"></a>
|
||||
## Support in Windows Presentation Foundation
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ while (true)
|
|||
This code generates stock information and then uses the service contract IStockTicker to send multicast messages to call services listening on the correct UDP address.
|
||||
|
||||
### UDP and Reliable Messaging
|
||||
The UDP binding does not support reliable messaging because of the lightweight nature of the UDP protocol. If you need to confirm that messages are received by a remote endpoint, use a transport that supports reliable messaging like HTTP or TCP. For more information about reliable messaging see https://go.microsoft.com/fwlink/?LinkId=231830
|
||||
The UDP binding does not support reliable messaging because of the lightweight nature of the UDP protocol. If you need to confirm that messages are received by a remote endpoint, use a transport that supports reliable messaging like HTTP or TCP. For more information about reliable messaging, see <https://go.microsoft.com/fwlink/?LinkId=231830>.
|
||||
|
||||
### Two-way Multicast Messaging
|
||||
While multicast messages are generally one-way, the UdpBinding does support request/reply message exchange. Messages sent using the UDP transport contain both a From and To address. Care must be taken when using the From address as it could be maliciously changed en-route. The address can be checked using the following code:
|
||||
|
|
|
|||
|
|
@ -30,9 +30,9 @@ The Windows Process Activation Service (WAS) manages the activation and lifetime
|
|||
|
||||
|Scenario|Site bindings|Application path|Base application URIs|
|
||||
|--------------|-------------------|----------------------|---------------------------|
|
||||
|HTTP Only|http: *:80:\*|/appTwo|http://localhost/appTwo/|
|
||||
|Both HTTP and Non-HTTP|http: *:80:\*<br /><br /> net.tcp: 808:\*|/appTwo|http://localhost/appTwo/<br />net.tcp://localhost/appTwo/|
|
||||
|Non-HTTP only|net.pipe: *|/appThree|net.pipe://appThree/|
|
||||
|HTTP Only|http: *:80:\*|/appTwo|`http://localhost/appTwo/`|
|
||||
|Both HTTP and Non-HTTP|http: *:80:\*<br /><br /> net.tcp: 808:\*|/appTwo|`http://localhost/appTwo/`<br />`net.tcp://localhost/appTwo/`|
|
||||
|Non-HTTP only|net.pipe: *|/appThree|`net.pipe://appThree/`|
|
||||
|
||||
Services and resources within an application can also be addressed. Within an application, application resources are addressed relative to the base application path. For example, assume that a site on a machine name contoso.com has site bindings for both the HTTP and Net.TCP protocols. Also assume that the site contains one application located at /Billing, which exposes a service at GetOrders.svc. Then, if the GetOrders.svc service exposed an endpoint with a relative address of SecureEndpoint, the service endpoint would be exposed at the following two URIs:
|
||||
|
||||
|
|
|
|||
|
|
@ -152,7 +152,7 @@ namespace Metadata.Samples
|
|||
|
||||
9. Build and run the console application.
|
||||
|
||||
10. Use Internet Explorer to browse to the base address of the service (http://localhost:8001/MetadataSample in this sample) and verify that the metadata publishing is turned on. If not, a message at the top of the resulting page displays: "Metadata publishing for this service is currently disabled."
|
||||
10. Use Internet Explorer to browse to the base address of the service (`http://localhost:8001/MetadataSample` in this sample) and verify that the metadata publishing is turned on. If not, a message at the top of the resulting page displays: "Metadata publishing for this service is currently disabled."
|
||||
|
||||
### To use default endpoints
|
||||
|
||||
|
|
|
|||
|
|
@ -72,7 +72,7 @@ This is one of two how-to topics that discuss publishing metadata for a Windows
|
|||
|
||||
10. Build and run the console application.
|
||||
|
||||
11. Use Internet Explorer to browse to the base address of the service (http://localhost:8001/MetadataSample in this sample) and verify that the metadata publishing is turned on. You should see a Web page displayed that says "Simple Service" at the top and immediately below "You have created a service." If not, a message at the top of the resulting page displays: "Metadata publishing for this service is currently disabled."
|
||||
11. Use Internet Explorer to browse to the base address of the service (`http://localhost:8001/MetadataSample` in this sample) and verify that the metadata publishing is turned on. You should see a Web page displayed that says "Simple Service" at the top and immediately below "You have created a service." If not, a message at the top of the resulting page displays: "Metadata publishing for this service is currently disabled."
|
||||
|
||||
## Example
|
||||
The following code example shows the implementation of a basic WCF service that publishes metadata for the service in code.
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ The Windows Communication Foundation (WCF) Service Moniker allows COM applicatio
|
|||
|
||||
4. Add `bindingNamespace="http://Microsoft.ServiceModel.Samples"` to the endpoint tag in the App.config for the service.
|
||||
|
||||
5. Build the Message Security Sample and run Service.exe. Use Internet Explorer and browse to the service's URI (http://localhost:8000/ServiceModelSamples/Service) to ensure that the service is working.
|
||||
5. Build the Message Security Sample and run Service.exe. Use Internet Explorer and browse to the service's URI (`http://localhost:8000/ServiceModelSamples/Service`) to ensure that the service is working.
|
||||
|
||||
6. Open Visual Basic 6.0 and create a new Standard .exe file. Add a button to the form and double-click the button to add the following code to the Click handler:
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ After developing some new WCF services, you may decide that you want to be able
|
|||
|
||||
### Using the service moniker with a Mex address
|
||||
|
||||
1. Build the Getting Started sample and use Internet Explorer to browse to its URL (http://localhost/ServiceModelSamples/Service.svc) to ensure that the service is working.
|
||||
1. Build the Getting Started sample and use Internet Explorer to browse to its URL (`http://localhost/ServiceModelSamples/Service.svc`) to ensure that the service is working.
|
||||
|
||||
2. Create a Visual Basic script or Visual Basic application that contains the following code:
|
||||
|
||||
|
|
|
|||
|
|
@ -19,11 +19,11 @@ This document uses the prefixes and namespaces in the following table.
|
|||
|
||||
|Prefix|Namespace|
|
||||
|------------|---------------|
|
||||
|wsrm|http://schemas.xmlsoap.org/ws/2005/02/rm|
|
||||
|netrm|http://schemas.microsoft.com/ws/2006/05/rm|
|
||||
|s|http://www.w3.org/2003/05/soap-envelope|
|
||||
|wsa|http://schemas.xmlsoap.org/ws/2005/08/addressing|
|
||||
|wsse|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssecurity-secext-1.0.xsd|
|
||||
|wsrm|`http://schemas.xmlsoap.org/ws/2005/02/rm`|
|
||||
|netrm|`http://schemas.microsoft.com/ws/2006/05/rm`|
|
||||
|s|`http://www.w3.org/2003/05/soap-envelope`|
|
||||
|wsa|`http://schemas.xmlsoap.org/ws/2005/08/addressing|
|
||||
|wsse|`http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssecurity-secext-1.0.xsd`|
|
||||
|
||||
## Messaging
|
||||
|
||||
|
|
|
|||
|
|
@ -19,13 +19,13 @@ For convenience, the topic uses the following roles:
|
|||
|
||||
|Prefix|Namespace|
|
||||
|-|-|
|
||||
|wsrm|http://docs.oasis-open.org/ws-rx/wsrm/200702|
|
||||
|netrm|http://schemas.microsoft.com/ws/2006/05/rm|
|
||||
|s|http://www.w3.org/2003/05/soap-envelope|
|
||||
|wsa|http://schemas.xmlsoap.org/ws/2005/08/addressing|
|
||||
|wsse|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssecurity-secext-1.0.xsd|
|
||||
|wsrmp|http://docs.oasis-open.org/ws-rx/wsrmp/200702|
|
||||
|netrmp|http://schemas.microsoft.com/ws-rx/wsrmp/200702|
|
||||
|wsrm|`http://docs.oasis-open.org/ws-rx/wsrm/200702`|
|
||||
|netrm|`http://schemas.microsoft.com/ws/2006/05/rm`|
|
||||
|s|`http://www.w3.org/2003/05/soap-envelope`|
|
||||
|wsa|`http://schemas.xmlsoap.org/ws/2005/08/addressing`|
|
||||
|wsse|`http://docs.oasis-open.org/wss/2004/01/oasis-200401-wssecurity-secext-1.0.xsd`|
|
||||
|wsrmp|`http://docs.oasis-open.org/ws-rx/wsrmp/200702`|
|
||||
|netrmp|`http://schemas.microsoft.com/ws-rx/wsrmp/200702`|
|
||||
|wsp|(Either WS-Policy 1.2 or WS-Policy 1.5)|
|
||||
|
||||
## Messaging
|
||||
|
|
|
|||
|
|
@ -10,21 +10,21 @@ The Web Services Security Protocols provide Web services security mechanisms tha
|
|||
|
||||
|Specification/Document|Link|
|
||||
|-|-|
|
||||
|WSS: SOAP Message Security 1.0|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf|
|
||||
|WSS: Username Token Profile 1.0|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf|
|
||||
|WSS: X509 Token Profile 1.0|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf|
|
||||
|WSS: SAML 1.1 Token Profile 1.0|http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0.pdf|
|
||||
|WSS: SOAP Message Security 1.1|http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf|
|
||||
|WSS Username Token Profile 1.1|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf|
|
||||
|WSS: X.509 Token Profile 1.1|http://www.oasis-open.org/committees/download.php/16785/wss-v1.1-spec-os-x509TokenProfile.pdf|
|
||||
|WSS: Kerberos Token Profile 1.1|http://www.oasis-open.org/committees/download.php/16788/wss-v1.1-spec-os-KerberosTokenProfile.pdf|
|
||||
|WSS: SAML 1.1 Token Profile 1.1|http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf|
|
||||
|WS-Secure Conversation 1.3|http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-os.pdf|
|
||||
|WS-Trust 1.3|http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.pdf|
|
||||
|WSS: SOAP Message Security 1.0|<http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf>|
|
||||
|WSS: Username Token Profile 1.0|<http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf>|
|
||||
|WSS: X509 Token Profile 1.0|<http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf>|
|
||||
|WSS: SAML 1.1 Token Profile 1.0|<http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0.pdf>|
|
||||
|WSS: SOAP Message Security 1.1|<http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf>|
|
||||
|WSS Username Token Profile 1.1|<http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf>|
|
||||
|WSS: X.509 Token Profile 1.1|<http://www.oasis-open.org/committees/download.php/16785/wss-v1.1-spec-os-x509TokenProfile.pdf>|
|
||||
|WSS: Kerberos Token Profile 1.1|<http://www.oasis-open.org/committees/download.php/16788/wss-v1.1-spec-os-KerberosTokenProfile.pdf>|
|
||||
|WSS: SAML 1.1 Token Profile 1.1|<http://www.oasis-open.org/committees/download.php/16768/wss-v1.1-spec-os-SAMLTokenProfile.pdf>|
|
||||
|WS-Secure Conversation 1.3|<http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512/ws-secureconversation-1.3-os.pdf>|
|
||||
|WS-Trust 1.3|<http://docs.oasis-open.org/ws-sx/ws-trust/200512/ws-trust-1.3-os.pdf>|
|
||||
|Application Note:<br /><br /> Using WS-Trust for TLS Handshake|To be published|
|
||||
|Application Note:<br /><br /> Using WS-Trust for SPNEGO|To be published|
|
||||
|Application Note:<br /><br /> Web Services Addressing Endpoint References And Identity|To be published|
|
||||
|WS-SecurityPolicy 1.2 (2007/04)|http://www.oasis-open.org/committees/download.php/23821/ws-securitypolicy-1.2-spec-cs.pdf|
|
||||
|WS-SecurityPolicy 1.2 (2007/04)|<http://www.oasis-open.org/committees/download.php/23821/ws-securitypolicy-1.2-spec-cs.pdf>|
|
||||
|
||||
WCF, version 1, provides 17 authentication modes that can be used as the basis for Web services security configuration. Each mode is optimized for a common set of deployment requirements, such as:
|
||||
|
||||
|
|
@ -64,18 +64,18 @@ The Web Services Security Protocols provide Web services security mechanisms tha
|
|||
|
||||
|Prefix|Namespace|
|
||||
|------------|---------------|
|
||||
|s|http://www.w3.org/2003/05/soap-envelope|
|
||||
|sp|http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702|
|
||||
|a|http://www.w3.org/2005/08/addressing|
|
||||
|s|`http://www.w3.org/2003/05/soap-envelope`|
|
||||
|sp|`http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702`|
|
||||
|a|`http://www.w3.org/2005/08/addressing`|
|
||||
|wsse|TBD – OASIS WSS 1.0 URI|
|
||||
|wsse11|TBD – OASIS WSS 1.1 URI|
|
||||
|wsu|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd|
|
||||
|wsu|`http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd`|
|
||||
|ds|TBD – W3C XMLDSig URI|
|
||||
|wst|TBD – WS-Trust 2005/02 URI|
|
||||
|wssc|TBD – WS-SecureConversation 2005/02 URI|
|
||||
|wsaw|http://www.w3.org/2006/05/addressing/wsdl|
|
||||
|wsp|http://schemas.xmlsoap.org/ws/2004/09/policy|
|
||||
|mssp|http://schemas.microsoft.com/ws/2005/07/securitypolicy|
|
||||
|wsaw|`http://www.w3.org/2006/05/addressing/wsdl`|
|
||||
|wsp|`http://schemas.xmlsoap.org/ws/2004/09/policy`|
|
||||
|mssp|`http://schemas.microsoft.com/ws/2005/07/securitypolicy`|
|
||||
|
||||
## 1. Token Profiles
|
||||
Web Services Security specifications represent credential as security tokens. WCF supports the following token types:
|
||||
|
|
|
|||
|
|
@ -203,7 +203,7 @@ To reduce the size of JSON messages, the default data contract namespace prefix
|
|||
{"__type":"Circle:#MyApp.Shapes","x":50,"y":70,"radius":10}
|
||||
```
|
||||
|
||||
Both the truncated (#MyApp.Shapes) and the full (http://schemas.datacontract.org/2004/07/MyApp.Shapes) names is understood on deserialization.
|
||||
Both the truncated (#MyApp.Shapes) and the full (<http://schemas.datacontract.org/2004/07/MyApp.Shapes>) names is understood on deserialization.
|
||||
|
||||
#### Type Hint Position in JSON Objects
|
||||
|
||||
|
|
|
|||
|
|
@ -53,13 +53,13 @@ Windows Communication Foundation (WCF) version 1 implements version 1.0 of the W
|
|||
|
||||
|Prefix|Namespace URI|
|
||||
|------------|-------------------|
|
||||
|s11|http://schemas.xmlsoap.org/soap/envelope|
|
||||
|wsa|http://www.w3.org/2004/08/addressing|
|
||||
|wscoor|http://schemas.xmlsoap.org/ws/2004/10/wscoor|
|
||||
|wsat|http://schemas.xmlsoap.org/ws/2004/10/wsat|
|
||||
|t|http://schemas.xmlsoap.org/ws/2005/02/trust|
|
||||
|o|http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd|
|
||||
|xsd|http://www.w3.org/2001/XMLSchema|
|
||||
|s11|`http://schemas.xmlsoap.org/soap/envelope`|
|
||||
|wsa|`http://www.w3.org/2004/08/addressing`|
|
||||
|wscoor|`http://schemas.xmlsoap.org/ws/2004/10/wscoor`|
|
||||
|wsat|`http://schemas.xmlsoap.org/ws/2004/10/wsat`|
|
||||
|t|`http://schemas.xmlsoap.org/ws/2005/02/trust`|
|
||||
|o|`http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd`|
|
||||
|xsd|`http://www.w3.org/2001/XMLSchema`|
|
||||
|
||||
## Transaction Manager Bindings
|
||||
R1001: Transaction Managers must use SOAP 1.1 and WS-Addressing 2004/08 for WS-Atomic Transaction and WS-Coordination message exchanges.
|
||||
|
|
|
|||
|
|
@ -36,15 +36,15 @@ Web developers require the ability to describe the shape and layout of the URIs
|
|||
|
||||
<xref:System.UriTemplate> is designed to work with any URI scheme that conforms to the HTTP URI grammar. The following are examples of supported URI schemes.
|
||||
|
||||
- http://
|
||||
- `http://`
|
||||
|
||||
- https://
|
||||
- `https://`
|
||||
|
||||
- net.tcp://
|
||||
- `net.tcp://`
|
||||
|
||||
- net.pipe://
|
||||
- `net.pipe://`
|
||||
|
||||
- sb://
|
||||
- `sb://`
|
||||
|
||||
Schemes like file:// and urn:// do not conform to the HTTP URI grammar and cause unpredictable results when used with URI templates.
|
||||
|
||||
|
|
|
|||
|
|
@ -12,14 +12,14 @@ This topic covers Windows Communication Foundation (WCF) WSDL 1.1, WS-Policy and
|
|||
|
||||
|Prefix|Namespace|
|
||||
|------------|---------------|
|
||||
|wsp (WS-Policy 1.2)|http://schemas.xmlsoap.org/ws/2004/09/policy|
|
||||
|wsp (WS-Policy 1.5)|http://www.w3.org/ns/ws-policy|
|
||||
|http|http://schemas.microsoft.com/ws/06/2004/policy/http|
|
||||
|msmq|http://schemas.microsoft.com/ws/06/2004/mspolicy/msmq|
|
||||
|msf|http://schemas.microsoft.com/ws/2006/05/framing/policy|
|
||||
|mssp|http://schemas.microsoft.com/ws/2005/07/securitypolicy|
|
||||
|msc|http://schemas.microsoft.com/ws/2005/12/wsdl/contract|
|
||||
|cdp|http://schemas.microsoft.com/net/2006/06/duplex|
|
||||
|wsp (WS-Policy 1.2)|`http://schemas.xmlsoap.org/ws/2004/09/policy`|
|
||||
|wsp (WS-Policy 1.5)|`http://www.w3.org/ns/ws-policy`|
|
||||
|http|`http://schemas.microsoft.com/ws/06/2004/policy/http`|
|
||||
|msmq|`http://schemas.microsoft.com/ws/06/2004/mspolicy/msmq`|
|
||||
|msf|`http://schemas.microsoft.com/ws/2006/05/framing/policy`|
|
||||
|mssp|`http://schemas.microsoft.com/ws/2005/07/securitypolicy`|
|
||||
|msc|`http://schemas.microsoft.com/ws/2005/12/wsdl/contract`|
|
||||
|cdp|`http://schemas.microsoft.com/net/2006/06/duplex`|
|
||||
|
||||
## WCF WSDL1.1 Extensions
|
||||
WCF uses the following WSDL1.1 extensions to describe contract session requirements.
|
||||
|
|
@ -38,10 +38,10 @@ This topic covers Windows Communication Foundation (WCF) WSDL 1.1, WS-Policy and
|
|||
|
||||
|Transport|URI|
|
||||
|---------------|---------|
|
||||
|HTTP|http://schemas.xmlsoap.org/soap/http|
|
||||
|TCP|http://schemas.microsoft.com/soap/tcp|
|
||||
|MSMQ|http://schemas.microsoft.com/soap/msmq|
|
||||
|Named Pipes|http://schemas.microsoft.com/soap/named-pipe|
|
||||
|HTTP|`http://schemas.xmlsoap.org/soap/http`|
|
||||
|TCP|`http://schemas.microsoft.com/soap/tcp`|
|
||||
|MSMQ|`http://schemas.microsoft.com/soap/msmq`|
|
||||
|Named Pipes|`http://schemas.microsoft.com/soap/named-pipe`|
|
||||
|
||||
## Policy Assertions Implemented by WCF
|
||||
In addition to policy assertions introduced in the Web Services specifications (WS-*) and mentioned in other sections of this document, WCF implements the following policy assertions.
|
||||
|
|
|
|||
|
|
@ -50,7 +50,7 @@ The program code in the sample is identical to that of the [Getting Started](../
|
|||
</system.serviceModel>
|
||||
```
|
||||
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an HTTPS: address in your browser, such as https://localhost/servicemodelsamples/service.svc. To allow the Windows Communication Foundation (WCF) client to work with a test certificate, some additional code is added to the client to suppress the security alert. This code, and the accompanying class, is not necessary when using real certificates.
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an HTTPS: address in your browser, such as `https://localhost/servicemodelsamples/service.svc`. To allow the Windows Communication Foundation (WCF) client to work with a test certificate, some additional code is added to the client to suppress the security alert. This code, and the accompanying class, is not necessary when using real certificates.
|
||||
|
||||
```csharp
|
||||
// This code is required only for test certificates such as those
|
||||
|
|
|
|||
|
|
@ -94,9 +94,9 @@ This sample demonstrates the use of SSL transport security with Reliable Session
|
|||
</configuration>
|
||||
```
|
||||
|
||||
The address specified uses the https:// scheme.
|
||||
The address specified uses the `https://` scheme.
|
||||
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an https: address, such as https://localhost/servicemodelsamples/service.svc, from your browser. To allow the Windows Communication Foundation (WCF) client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. This code, and the accompanying class, is not required when using production certificates.
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an https: address, such as `https://localhost/servicemodelsamples/service.svc`, from your browser. To allow the Windows Communication Foundation (WCF) client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. This code, and the accompanying class, is not required when using production certificates.
|
||||
|
||||
```csharp
|
||||
// This code is required only for test certificates like those created by Makecert.exe.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ The Discovery specification does not require that endpoints that participate in
|
|||
> [!NOTE]
|
||||
> The `PrefixList` was added in the 2008 Discovery version protocol.
|
||||
|
||||
To compute the signature, the sample determines the expanded signature items. An XML signature (`SignedInfo`) is created, using the `ds` namespace prefix, as required by the WS-Discovery specification. The body and all the headers in discovery and addressing namespaces are referenced in the signature, so they cannot be tampered with. Each referenced element is transformed using the Exclusive Canonicalization (http://www.w3.org/2001/10/xml-exc-c14n# ), and then an SHA-1 digest value is computed (http://www.w3.org/2000/09/xmldsig#sha1 ). Based on all referenced elements and their digest values, the signature value is computed using the RSA algorithm (http://www.w3.org/2000/09/xmldsig#rsa-sha1 ).
|
||||
To compute the signature, the sample determines the expanded signature items. An XML signature (`SignedInfo`) is created, using the `ds` namespace prefix, as required by the WS-Discovery specification. The body and all the headers in discovery and addressing namespaces are referenced in the signature, so they cannot be tampered with. Each referenced element is transformed using the Exclusive Canonicalization (<http://www.w3.org/2001/10/xml-exc-c14n#>), and then an SHA-1 digest value is computed (<http://www.w3.org/2000/09/xmldsig#sha1>). Based on all referenced elements and their digest values, the signature value is computed using the RSA algorithm (<http://www.w3.org/2000/09/xmldsig#rsa-sha1>).
|
||||
|
||||
The messages are signed with a client-specified certificate. The store location, name, and certificate subject name must be specified when the binding element is created. The `KeyId` in the compact signature represents the key identifier of the signing token and is the Subject Key Identifier (SKI) of the signing token or (if the SKI does not exist) a SHA-1 hash of the public key of the signing token.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,9 +43,9 @@ This sample demonstrates the use of SSL transport security with the <xref:System
|
|||
</system.serviceModel>
|
||||
```
|
||||
|
||||
The address specified uses the https:// scheme. The binding configuration sets the security mode to `Transport`. The same security mode must be specified in the service's Web.config file.
|
||||
The address specified uses the `https://` scheme. The binding configuration sets the security mode to `Transport`. The same security mode must be specified in the service's Web.config file.
|
||||
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an https: address, such as https://localhost/servicemodelsamples/service.svc, from your browser. To allow the Windows Communication Foundation (WCF) client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. This code, and the accompanying class, is not required when using production certificates.
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an https: address, such as `https://localhost/servicemodelsamples/service.svc`, from your browser. To allow the Windows Communication Foundation (WCF) client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. This code, and the accompanying class, is not required when using production certificates.
|
||||
|
||||
```csharp
|
||||
// This code is required only for test certificates like those created by Makecert.exe.
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ public string GetCallerIdentity()
|
|||
</system.serviceModel>
|
||||
```
|
||||
|
||||
The address specified uses the https:// scheme. The binding configuration sets the security mode to `TransportWithMessageCredential`. The same security mode must be specified in the service's Web.config file.
|
||||
The address specified uses the `https://` scheme. The binding configuration sets the security mode to `TransportWithMessageCredential`. The same security mode must be specified in the service's Web.config file.
|
||||
|
||||
Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert appears when you try to access an https: address, such as `https://localhost/servicemodelsamples/service.svc`, from your browser. To allow the WCF client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. This code, and the accompanying class, is not required when using production certificates.
|
||||
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@ public class StreamedEchoService : IStreamedEchoService
|
|||
|
||||
## The WSStreamedHttpBinding Sample Client
|
||||
|
||||
The client that is used to interact with the service using `WSStreamedHttpBinding` is located in the client subdirectory. Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert displays when you attempt to access an HTTPS address in your browser such as https://localhost/servicemodelsamples/service.svc. To allow the WCF client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. The code and the accompanying class are not required when using production certificates.
|
||||
The client that is used to interact with the service using `WSStreamedHttpBinding` is located in the client subdirectory. Because the certificate used in this sample is a test certificate created with Makecert.exe, a security alert displays when you attempt to access an HTTPS address in your browser such as `https://localhost/servicemodelsamples/service.svc`. To allow the WCF client to work with a test certificate in place, some additional code has been added to the client to suppress the security alert. The code and the accompanying class are not required when using production certificates.
|
||||
|
||||
```csharp
|
||||
// WARNING: This code is only required for test certificates such as those created by makecert. It is
|
||||
|
|
|
|||
|
|
@ -41,7 +41,7 @@ The tracking participant subscribes for a subset of the emitted tracking records
|
|||
|
||||
3. To run the solution, press F5.
|
||||
|
||||
By default, the service is listening on port 53797 (http://localhost:53797/SampleWorkflowService.xamlx).
|
||||
By default, the service is listening on port 53797 (`http://localhost:53797/SampleWorkflowService.xamlx`).
|
||||
|
||||
4. Using File Explorer, open the WCF test client.
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ You can make use of the <xref:System.Windows.Forms.HelpProvider> component to at
|
|||
|
||||
At run time, pressing F1 when the control—for which you have set the **HelpKeyword** and **HelpNavigator** properties—has focus will open the Help file you associated with that <xref:System.Windows.Forms.HelpProvider> component.
|
||||
|
||||
Currently, the **HelpNamespace** property supports Help files in the following three formats: HTMLHelp 1.x, HTMLHelp 2.0, and HTML. Thus, you can set the **HelpNamespace** property to an http:// address, such as a Web page. If this is done, it will open the default browser to the Web page with the string specified in the **HelpKeyword** property used as the anchor. The anchor is used to jump to a specific part of an HTML page.
|
||||
Currently, the **HelpNamespace** property supports Help files in the following three formats: HTMLHelp 1.x, HTMLHelp 2.0, and HTML. Thus, you can set the **HelpNamespace** property to an `http://` address, such as a Web page. If this is done, it will open the default browser to the Web page with the string specified in the **HelpKeyword** property used as the anchor. The anchor is used to jump to a specific part of an HTML page.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> Be careful to check any information that is sent from a client before using it in your application. Malicious users might try to send or inject executable script, SQL statements, or other code. Before you display a user's input, store it in a database, or work with it, check that it does not contain potentially unsafe information. A typical way to check is to use a regular expression to look for keywords such as "SCRIPT" when you receive input from a user.
|
||||
|
|
|
|||
|
|
@ -177,11 +177,11 @@ Microsoft Windows applications often depend on files that contain non-executable
|
|||
|
||||
- Your application uses large data files, such as audio and video, and you only want users to download them if they choose to.
|
||||
|
||||
It is possible to load these types of files by using traditional URI schemes, such as the file:/// and http:// schemes.
|
||||
It is possible to load these types of files by using traditional URI schemes, such as the `file:///` and `http://` schemes.
|
||||
|
||||
[!code-xaml[WPFAssemblyResourcesSnippets#AbsolutePackUriFileHttpReferenceXAML](~/samples/snippets/csharp/VS_Snippets_Wpf/WPFAssemblyResourcesSnippets/CSharp/ResourcesSample/AbsolutePackUriPage.xaml#absolutepackurifilehttpreferencexaml)]
|
||||
|
||||
However, the file:/// and http:// schemes require your application to have full trust. If your application is a XAML browser application (XBAP) that was launched from the Internet or intranet, and it requests only the set of permissions that are allowed for applications launched from those locations, loose files can only be loaded from the application's site of origin (launch location). Such files are known as *site of origin* files.
|
||||
However, the `file:///` and `http://` schemes require your application to have full trust. If your application is a XAML browser application (XBAP) that was launched from the Internet or intranet, and it requests only the set of permissions that are allowed for applications launched from those locations, loose files can only be loaded from the application's site of origin (launch location). Such files are known as *site of origin* files.
|
||||
|
||||
Site of origin files are the only option for partial trust applications, although are not limited to partial trust applications. Full trust applications may still need to load application data files that they do not know about at build time; while full trust applications could use file:///, it is likely that the application data files will be installed in the same folder as, or a subfolder of, the application assembly. In this case, using site of origin referencing is easier than using file:///, because using file:/// requires you to work out the full path the file.
|
||||
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ A [supervised machine learning](glossary.md#supervised-machine-learning) task th
|
|||
For more information, see the [Multiclass classification](https://en.wikipedia.org/wiki/Multiclass_classification) article on Wikipedia.
|
||||
|
||||
>[!NOTE]
|
||||
>One vs all upgrades any [binary classification learner](#binary-classification) to act on multiclass datasets. More information on [Wikipedia] (https://en.wikipedia.org/wiki/Multiclass_classification#One-vs.-rest).
|
||||
>One vs all upgrades any [binary classification learner](#binary-classification) to act on multiclass datasets. More information on [Wikipedia](https://en.wikipedia.org/wiki/Multiclass_classification#One-vs.-rest).
|
||||
|
||||
### Multiclass classification trainers
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ Now that you have a general understanding of transfer learning and the Image Cla
|
|||
### Prepare and understand the data
|
||||
|
||||
> [!NOTE]
|
||||
> The datasets for this tutorial are from Maguire, Marc; Dorafshan, Sattar; and Thomas, Robert J., "SDNET2018: A concrete crack image dataset for machine learning applications" (2018). Browse all Datasets. Paper 48. https://digitalcommons.usu.edu/all_datasets/48
|
||||
> The datasets for this tutorial are from Maguire, Marc; Dorafshan, Sattar; and Thomas, Robert J., "SDNET2018: A concrete crack image dataset for machine learning applications" (2018). Browse all Datasets. Paper 48. <https://digitalcommons.usu.edu/all_datasets/48>
|
||||
|
||||
SDNET2018 is an image dataset that contains annotations for cracked and non-cracked concrete structures (bridge decks, walls, and pavement).
|
||||
|
||||
|
|
|
|||
|
|
@ -61,9 +61,9 @@ Image Classification is a common Machine Learning task that allows us to automat
|
|||
>[!Note]
|
||||
> The preceding images belong to Wikimedia Commons and are attributed as follows:
|
||||
>
|
||||
> * "220px-Pepperoni_pizza.jpg" Public Domain, https://commons.wikimedia.org/w/index.php?curid=79505,
|
||||
> * "119px-Nalle_-_a_small_brown_teddy_bear.jpg" By [Jonik](https://commons.wikimedia.org/wiki/User:Jonik) - Self-photographed, CC BY-SA 2.0, https://commons.wikimedia.org/w/index.php?curid=48166.
|
||||
> * "193px-Broodrooster.jpg" By [M.Minderhoud](https://nl.wikipedia.org/wiki/Gebruiker:Michiel1972) - Own work, CC BY-SA 3.0, https://commons.wikimedia.org/w/index.php?curid=27403
|
||||
> * "220px-Pepperoni_pizza.jpg" Public Domain, <https://commons.wikimedia.org/w/index.php?curid=79505>,
|
||||
> * "119px-Nalle_-_a_small_brown_teddy_bear.jpg" By [Jonik](https://commons.wikimedia.org/wiki/User:Jonik) - Self-photographed, CC BY-SA 2.0, <https://commons.wikimedia.org/w/index.php?curid=48166>.
|
||||
> * "193px-Broodrooster.jpg" By [M.Minderhoud](https://nl.wikipedia.org/wiki/Gebruiker:Michiel1972) - Own work, CC BY-SA 3.0, <https://commons.wikimedia.org/w/index.php?curid=27403>
|
||||
|
||||
The `Inception model` is trained to classify images into a thousand categories, but for this tutorial, you need to classify images in a smaller category set, and only those categories. Enter the `transfer` part of `transfer learning`. You can transfer the `Inception model`'s ability to recognize and classify images to the new limited categories of your custom image classifier.
|
||||
|
||||
|
|
@ -106,9 +106,9 @@ toaster2.png appliance
|
|||
|
||||
The training and testing images are located in the assets folders that you'll download in a zip file. These images belong to Wikimedia Commons.
|
||||
> *[Wikimedia Commons](https://commons.wikimedia.org/w/index.php?title=Main_Page&oldid=313158208), the free media repository.* Retrieved 10:48, October 17, 2018 from:
|
||||
> https://commons.wikimedia.org/wiki/Pizza
|
||||
> https://commons.wikimedia.org/wiki/Toaster
|
||||
> https://commons.wikimedia.org/wiki/Teddy_bear
|
||||
> <https://commons.wikimedia.org/wiki/Pizza>
|
||||
> <https://commons.wikimedia.org/wiki/Toaster>
|
||||
> <https://commons.wikimedia.org/wiki/Teddy_bear>
|
||||
|
||||
## Setup
|
||||
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@ Once your cluster is running and you've uploaded your files to Azure, you run th
|
|||
|---------|---------|
|
||||
| Script type |Custom|
|
||||
| Name | Install Worker|
|
||||
| Bash script URI |https://mystorageaccount.blob.core.windows.net/mycontainer/install-worker.sh </br> To confirm this URI, right-click on install-worker.sh in Azure Storage Explorer and select Properties. |
|
||||
| Bash script URI |`https://mystorageaccount.blob.core.windows.net/mycontainer/install-worker.sh` </br> To confirm this URI, right-click on install-worker.sh in Azure Storage Explorer and select Properties. |
|
||||
| Node type(s)| Worker|
|
||||
| Parameters | azure </br> wasbs://mycontainer@myStorageAccount.blob.core.windows.net/Microsoft.Spark.Worker.netcoreapp2.1.linux-x64-0.6.0.tar.gz </br> /usr/local/bin
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ It won't be necessary for projects to consume assemblies in `Microsoft.AspNetCor
|
|||
|
||||
This change doesn't apply to all binaries referenced via `Microsoft.AspNetCore.App` in ASP.NET Core 2.x. Notable exceptions include:
|
||||
|
||||
- `Microsoft.Extensions` libraries that continue to target .NET Standard will be available as NuGet packages (see https://github.com/dotnet/extensions).
|
||||
- `Microsoft.Extensions` libraries that continue to target .NET Standard will be available as NuGet packages (see <https://github.com/dotnet/extensions>).
|
||||
- APIs produced by the ASP.NET Core team that aren't part of `Microsoft.AspNetCore.App`. For example, the following components are available as NuGet packages:
|
||||
- Entity Framework Core
|
||||
- APIs that provide third-party integration
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче