Comet system forum

palhal · 29-08-2019 15:00:18

When specifying a non-standard SOAP server port, the URL in the HTTP request made to the server is not properly formatted.

Example configuration:
SOAP server address: http://10.1.1.1/soap/comet.asmx
SOAP server port: 5000

At the server side, the following request is received:
POST http://10.1.1.1/soap/comet.asmx HTTP/1.1
Host: 10.1.1.1:5000

The first line includes the address, but not the port number. This results in a 400 Bad Request reply from the server.

The first line should either be:
POST /soap/comet.asmx HTTP/1.1
or
POST http://10.1.1.1:5000/soap/comet.asmx HTTP/1.1

If the port number is included in the SOAP server address parameter, the sensor does not connect to the server.

Is there a newer firmware available with this working correctly? Or is there a possibility to release a new one?

Hardware:
Type: P8641 (kind:1107H, type:40, ch:4, bin:0, unlock:0)
Fw: 4-5-8-1.3502 (Bay cat)

Last edited by palhal (29-08-2019 15:09:51)

HonzaD · 30-08-2019 09:06:26

Hi,

Inside your device you have a latest production firmware version. There is no newer version available for now.

Although use of POST Request-URI may to be slightly unusual, we believe that our implementation does not violate specification for http 1.1 protocol (RFC 2616).

We have validated our SOAP implementation (including using different port) with many web servers (Apache, IIS, Nginx, etc.). We did not found any compatibility issue. Also many our customers use SOAP with own http server without any issue. You are a first customer reporting such kind of compatibility issue. What exact type of web server do you use?

Please contact our support team directly. I think we will find a way how to improve compatibility with your web server.

Jan

palhal · 30-08-2019 14:52:29

Hi. Thank you for the prompt reply.

I am using Kestrel (ASP.NET Core) web server.

Section 5.2 (3rd paragraph) of the RFC states that the Host header should be ignored when using an absolute URI. Since the sensor requests an absolute URI, it doesn't help putting the port number in the Host header. In fact, the whole Host header should be omitted.

Why is there a separate SOAP server port parameter, and not a separate SOAP server host parameter? The host is clearly deduced from the address. The same could apply to the port number, and the requested URI would probably be correct.

Maybe it accidentally works for others if they have a web server listening on multiple ports, e.g. 80 and 5000, but this is not the case for me.

HonzaD · 02-09-2019 07:32:12

Hi,

Separate field for a port is from a history reasons. Because there are some other consequences of implementation.

Jan

Comet system forum

Temperature, Humdity,

Pressure Transmitters

and Data Loggers

#1 29-08-2019 15:00:18

Address in SOAP request not properly formatted

#2 30-08-2019 09:06:26

Re: Address in SOAP request not properly formatted

#3 30-08-2019 14:52:29

Re: Address in SOAP request not properly formatted

#4 02-09-2019 07:32:12

Re: Address in SOAP request not properly formatted

Board footer