Differences

This shows you the differences between two versions of the page.

--- webapi:implementations:udp [2025/01/30 08:56] – icke_siegen
+++ webapi:implementations:udp [2025/03/20 16:08] (current) – icke_siegen
@@ Line 1: / Line 1: @@
 ~~HEADLINE NUMBERING FIRST LEVEL = 3~~
-Titan Web-API
+Titan WebAPI
 ====== WebAPI over UDP ======
@@ Line 64: / Line 64: @@
   - The third line simply contains a linefeed (strictly the second linefeed after the one at the end of line 2), in order to mark the end of the request.
-May this does not work for all Web API requests - but it is a starting point to make it available over UDP.
+**Note that different UDP programs seem to handle line endings differently.**
+  * Microsoft's [[https://www.microsoft.com/de-at/p/udp-sender-reciever/9nblggh52bt0|UDP-Sender/Receiver]] seems to be unable to send linefeeds in the transmitted message; if you write them escaped (''\r\n'') then it dends the literal characters, and a normal linefeed (pressing the ENTER button) isn't reflected in the message at all
+  * the [[https://udp-test-tool.informer.com/|UDP Test Tool]] also sends escaped linefeeds as literal characters, causing Titan to reject this as '400 Bad Request'. However you can press ENTER instead of writing \r\n -- and this gets correctly transmitted as linefeed.\\ Here is a screenshot of the same string entered with pressing ENTER instead of writing the linefeeds:
+|{{:webapi:implementations:udp_linefeeds.png?600|}}|
+Here UDP Test Tool is shown with linefeeds in the ASCII text (hardly visible), and their representation (note the highlighted ''0D 0A'' sequences in the HEX view):
+{{:webapi:implementations:udp_tool_ascii.png?400|}}      {{:webapi:implementations:udp_tool_hex.png?400|}}
+Maybe this does not work for all Web API requests - but it is a starting point to make it available over UDP.