View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009044 | 10000-004: Services | Spec | public | 2023-07-14 04:19 | 2023-07-25 15:31 |
Reporter | Martin Regen | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | ||
Platform | .NET stack | ||||
Product Version | 1.04 | ||||
Summary | 0009044: Clarify use of the serverUri field in the CreateSession request | ||||
Description | A user of the .NET stack recently reported that the .NET stack is always sending the application Uri (server Uri) on the CreateSession service call and that the serverUri should be set to null instead as it is stated in the spec: https://reference.opcfoundation.org/Core/Part4/v104/docs/5.6.2.2 "This value is only specified if the EndpointDescription has a gatewayServerUri. The reporter claimed that he couldn't connect to a server when the field was set. However talking to the SDK vendor he claimed it should not be an issue, but it may be checked if the field is set. Sending the serverUri had been tested for years in the IOP and in the field and I'm not aware of any issues. If more SDK implement it this way, I would like to discuss if the text should be changed to allow to do it both ways as it seems to be 'de facto' standard. Are there specific CTT tests that validate the behavior to allow for setting the application Uri? see also https://github.com/OPCFoundation/UA-.NETStandard/pull/2193 | ||||
Tags | No tags attached. | ||||
Commit Version | |||||
Fix Due Date | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2023-07-14 04:19 | Martin Regen | New Issue | |
2023-07-25 15:30 | Jim Luth | Note Added: 0019721 | |
2023-07-25 15:31 | Jim Luth | Status | new => acknowledged |