@Escar 

Escar wrote

Hi, 

 

with an alarmserver configured in the camera, I only get messages without picture.

If I try to attach a picture the server can´t handle the message, because the Content-Disposition-Header is missing the "filename" information.

 

This is what we get from the camera:
 

Encapsulated multipart part:  (image/jpeg)

        Content-Disposition: form-data; name="20250510122831"

        Content-Type: image/jpeg

        Content-Length: 17903

        Media Type

 

In the second row there is only "name" after form-data, but our server awaits additionally the "filename".

Technically the "filename" is not necessary, but a lot of servers or frameworks needs "filename" to process the upload correctly.

 

Is it possible to add "filename" in the next firmware?

 

Best regards

 

Escar

So the file name now is the string of the date? You mean.

You need an additional filename, not sure what you mean. Any more description?

  @Clive_A 

The problem is that there is no file with a filename, because the server refuses to process the message and discards the file since the camera does not adhere to the standard defined in RFC 1867.

 

RFC 1867 (form-based file Upload in HTML) defines that the local "filename" should be supplied either als 'filename' either of the 'content-disposition: form-data' header or in the case of multiple files in a 'content-disposition: file' header of the subpart.

 

The camera does not supply the "filename" and therefore its behaviour is not RFC compliant, which is why my server (as most other servers) just discards the binary data (the file)...

 

Actually it sends this:

 

Encapsulated multipart part:  (image/jpeg)

        Content-Disposition: form-data; name="20250510122831"

        Content-Type: image/jpeg

        Content-Length: 17903

        Media Type

 

It should look like that:

 

Encapsulated multipart part:  (image/jpeg)

        Content-Disposition: form-data; name="20250510122831"; filename="20250510122831.jpg"

        Content-Type: image/jpeg

        Content-Length: 17903

        Media Type

 

Best regards

 

Escar

Hi @Escar

This is submitted as feedback to the related team.

 

Thank you for your feedback and post.  Since this is a new feedback/feature request, we will keep an eye on this request and collect more votes.
Feel free to vote for this feature and please describe your user case/scenario. For your requests, please understand that it might be some time before the request reaches a threshold with details and votes for an evaluation report.  During the collection of votes, we cannot update you as we would keep track of the vote and user case of a request post before the evaluation report is sent.   To stay updated on firmware releases, we recommend subscribing to the pinned thread on the related page or regularly checking our official website where new releases are typically announced promptly.
Please note that all requests undergo a thorough evaluation by our developer team before being added to the roadmap. This process may take some time, so please be patient if you don't see immediate results. Features with lower priority or fewer user reports might experience delays in implementation as we gather more feedback and compare it with competitor products.
It is important to understand that submitting a request does not guarantee its implementation; only requests that pass the evaluation will be considered for inclusion in future updates.

 

this is a essential feature in environments where individual monitoring tools are in use.

.

this is an essential feature and should not only be implemented through votes... also the implementation should not be that complicated and time consuming :/