dsanderbi opened a new issue, #5591:
URL: https://github.com/apache/hop/issues/5591

   ### Apache Hop version?
   
   2.14
   
   ### Java version?
   
   17
   
   ### Operating system
   
   Windows
   
   ### What happened?
   
   I encountered two issues while working with a Synchronous Service in Apache 
Hop:
   
   **1) Content-Type variable not resolved**
   
   When configuring the Content-Type in the service metadata, I’m using a 
variable (e.g. ${content_type}).
   
   <img width="410" height="251" alt="Image" 
src="https://github.com/user-attachments/assets/5b862831-801c-4067-b6cf-4c931aea028a";
 />
   
   
   I set the value of this variable in a pipeline/workflow that is in the 
service, but the Content-Type header is not being replaced with the actual 
value – the variable remains unresolved in the HTTP response.
   The example can be found here: 
[content-type.zip](https://github.com/user-attachments/files/21487948/content-type.zip)
   
   To run the example, unzip and copy paste it to your default project:
   
   1. Start the hop-server and request 
http://localhost:8080/hop/webService/?service=test
   2. You should get "blao" as a request result.
   3. If you check the headers you will see 
   
   
   <img width="989" height="198" alt="Image" 
src="https://github.com/user-attachments/assets/f8402032-c956-4f78-be54-0369b90d4ce0";
 />
   
   It seems that the variable doesn't get resolved.
   
   
   **2) Copy & Paste does not work**
   
   The Content-Type field in the service metadata editor does not support copy 
& paste (at least on my system). This makes it difficult to reuse or transfer 
values
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: Hop Server, Component: Metadata


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to