Skip to content

Update RemoteEndpointMessageProperty.xml #9125

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ronnelsantiago wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update RemoteEndpointMessageProperty.xml #9125

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion xml/System.ServiceModel.Channels/RemoteEndpointMessageProperty.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@

Availability of the property when using HTTP hosted in IIS depends on having a currently active request. Therefore, this property is not available after the request has completed, such as when performing a one-way receive.

The IP address and port number are that of the node from which the message was received. If a message goes through a relay or proxy, the IP address and port number of the respective relay or proxy is the one attached to the message by this property.
The IP address and port number are that of the node from which the message was sent. If a message goes through a relay or proxy, the IP address and port number of the respective relay or proxy is the one attached to the message by this property.

Be aware that the IP address and port could be spoofed by an attacker and thus should not be relied upon for security sensitive authentication or authorization unless additional application specific logic is added.

Expand Down