apache / apache/hop

[Bug]: REST Client - breaking change with proxy settings and REST Connection

Open
#8,099 2 comments 0 reactions 0 assignees View on GitHub
awaiting triage P3 Transforms
Dominant language
Java
Stars
1.5k
Forks
476
Avg merge
18h 32m
Merged PRs (30d)
216

Description

### Apache Hop version?

2.19

### Java version?

ZuluJDK 21

### Operating system

Linux

### What happened?

In Hop 2.19 the **REST Connection** metadata now includes settings for using a proxy to connect.

When using a "proxied" connection in a **REST Client**, the proxy settings in it are now disabled. If specified in a previous version of Hop, they are also ignored and need to be specified/moved in the selected connection.

_(yep, this is an auto-resolved bug... feel free to discard or use it to update any relevant documentation 😅)_

### Issue Priority

Priority: 3

### Issue Component

Component: Transforms

Contributor guide

Open the contributing guide

Research direction

Start by comparing the REST Connection proxy settings with the REST Client behavior described for Hop 2.19. Then inspect the relevant REST Client and REST Connection documentation and update it to explain where proxy settings now belong and how previous configurations are affected. Done means the current behavior and migration guidance are clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.