Endpoint - Revision history

Tom: /* Context */

2023-04-26T04:28:21Z

‎Context

2023-04-25T22:30:13Z

‎Context

2023-04-25T22:29:39Z

‎Context

2023-04-25T22:28:29Z

‎Problem

2023-04-25T22:14:25Z

‎Context

2023-04-25T22:12:08Z

‎Context

2023-04-25T22:10:33Z

‎Problem

2022-01-03T00:19:45Z

‎Problem

2022-01-03T00:03:51Z

‎Problem

2019-09-03T18:56:25Z

‎Context

@@ Line 3: / Line 3: @@
 ==Context==
-Endpoints have been defined in may standardized contexts.
+Endpoints have been defined in many standardized contexts.
 * [https://hl7.org/fhir/R4/endpoint.html The FHIR Resource Endpoint]
+*
@@ Line 13: / Line 13: @@
 # URL addresses which are converted to IP addresses by a [[DNS]]
 ## Web addresses which use the URL scheme HTTP:// or the preferred HTTPS:// These are the ones of particular interest here.
-## Other application specific URL schemes, like streaming media or datagram.
+## Other application specific URL schemes, like streaming media or data-gram.
 ==Problem==

@@ Line 12: / Line 12: @@
 ## IP V6
 # URL addresses which are converted to IP addresses by a [[DNS]]
-## Web addresses which use the URL scheme HTTP:// or the preferred HTTPS://
+## Web addresses which use the URL scheme HTTP:// or the preferred HTTPS:// These are the ones of particular interest here.
-## Other application specific URL schemes, like media or datagram.
+## Other application specific URL schemes, like streaming media or datagram.
 ==Problem==

@@ Line 13: / Line 13: @@
 # URL addresses which are converted to IP addresses by a [[DNS]]
 ## Web addresses which use the URL scheme HTTP:// or the preferred HTTPS://
 ==Problem==

@@ Line 23: / Line 23: @@
 Like any URL access point, and device [[Endpoint]] is subject to worldwide attacks.
-https://mail.google.com/mail/u/0/#inbox/FMfcgzGsmNNrVqFqFNrVWBRXNwglBWxH
+* [https://www.cisa.gov/news-events/alerts/2023/04/25/abuse-service-location-protocol-may-lead-dos-attacks Abuse of the Service Location Protocol (SLP, RFC 2608) may lead to DOS attacks.] (2023-04-25)
 ==Solution==

@@ Line 9: / Line 9: @@
 There are two broad classes of endpoints.
 # IP address
 # URL addresses which are converted to IP addresses by a [[DNS]]
 ## Web addresses which use the URL scheme HTTP:// or the preferred HTTPS://

@@ Line 7: / Line 7: @@
+*
 ==Problem==
-* It has been recognized for many years that [[URL]]s (and hence [[Endpoint]]s are poor substitutes for [[Web Site]] [[Identifier]]s<ref>Jakob Nielsen, ''URL as UI'' https://www.nngroup.com/articles/url-as-ui/</ref>. Yet no one has found a such a substitute.
+* It has been recognized for many years that [[URL]]s (and hence [[Endpoint]]s are poor substitutes for [[Web Site]] [[Identifier]]s<ref>Jakob Nielsen, ''URL as UI'' https://www.nngroup.com/articles/url-as-ui/</ref>. Yet no one has found a suitable substitute.
 * Many standards have been focused on setting new endpoints for every service defined by the web site.
-* Since endpoints are just URLs there ability to access sign in credentials or cookies is determined by policies set by the browser manufacturer or, possibly, by and administrator. These policy are subject to changes that are never explained, or even explainable, to the user.
+* Since endpoints are just URLs their ability to access sign in credentials or cookies is determined by policies set by the browser manufacturer or, possibly, by an administrator. These policies are subject to changes that are never explained, or even explainable, to the user.
 * Since endpoint policy is not under the control of the standards, there is no chance for them to make it really clear when an endpoint will be consider to be a part of the origin and thus not subject to cross-origin policies.
 ==Solution==