Setup of proxy to use the REST API

[ZinnerC]

Hi I'm currently setting up an instance of Inventree.
To make all the parts available I would like to use the REST API. Because I feel it to be easier to make batch changes to the data. At the moment I first would like to use a API client (Bruno) to test the functionallity.

I'm able to make requests to the server.
So far the following entpoints work for me:

• GET: http://{{domain}}/api/part/
• GET: http://{{domain}}/api/part/{{id}}/

But sadly the POST I'm looking forward does not work:
-POST: http://{{domain}}/api/part/{{id}}/
--> JSON (Body): {"name": "tester"}

The POST returns 200 and a list of existing parts. This on the instance I would like to use productively.
To make sure that I did not do anything wrong I quickly installed the same setup on a RaspberryPi locally to be sure that nothing "between" (e.g. proxy or firewall) is hindering the communication. And tada it works flawless.

Does anybody have an idea or suggestions what I could look out for to fix this issue?
Much appreciated!

With regard to the system I'm using:

Version Information:

InvenTree-Version: 0.17.1
Django Version: 4.2.17
Commit Hash: eed6223
Commit Date: 2024-12-26

Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-6.8.0-1020-azure-x86_64-with
Installer: DOC

Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.1.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'InvenTreeCurrencyExchange', 'slug': 'inventreecurrencyexchange', 'version': '1.0.0'}, {'name': 'InvenTreeLabel', 'slug': 'inventreelabel', 'version': '1.1.0'}, {'name': 'InvenTreeLabelMachine', 'slug': 'inventreelabelmachine', 'version': '1.0.0'}, {'name': 'InvenTreeLabelSheet', 'slug': 'inventreelabelsheet', 'version': '1.0.0'}, {'name': 'DigiKeyPlugin', 'slug': 'digikeyplugin', 'version': '1.0.0'}, {'name': 'LCSCPlugin', 'slug': 'lcscplugin', 'version': '1.0.0'}, {'name': 'MouserPlugin', 'slug': 'mouserplugin', 'version': '1.0.0'}, {'name': 'TMEPlugin', 'slug': 'tmeplugin', 'version': '1.0.0'}]

[matmair]

Sounds like you might have a WAF in between. Some of them rewrite requests; maybe look at differing response headers, they are often marked with info from the proxy provider.
This sounds very setup-specific - being a bit more specific about your deployment scenario and the network path from your browser might give clues to what is happening.

[ZinnerC]

Thanks for the previous response. After some checks on the server and what messages arrive. It showed that the application Bruno which has been used to test the API caused the issues. Simple tests with a Python script worked fine. Postman worked.

[matmair]

Thank you for the update