Skip to content

Conversation

@siddhantk232
Copy link
Contributor

@siddhantk232 siddhantk232 commented Sep 17, 2025

The http processor url should not be manipulated by current_request
properties. If the user code wants to inherit something from current
request then they should explicitly add that property to the url (or
custom headers) while using the http processor.

This is an immediate fix for the following situation:

An .ftd file for url /experts/?payment=true has a call to http processor
like this:

-- expert-detail-response res:
$processor$: pr.http
method: GET
url: /experts/?id=120

The http processor overrides the id query param with the current
request query params (payment=true), which is clearly wrong! The right
thing is to not manipulate the user provided url at all. If the user
want to append payment=true then they will have to change their ftd
code so that the url becomes "/experts/?id=120&payment=true".

The http processor `url` should not be manipulated by `current_request`
properties. If the user code wants to inherit something from current
request then they should explicitly add that property to the `url` (or
custom headers) while using the `http` processor.

This is an immediate fix for the following situation:

An .ftd file for url /experts/?payment=true has a call to http processor
like this:

```ftd
-- expert-detail-response res:
$processor$: pr.http
method: GET
url: /experts/?id=120
```

The http processor overrides the `id` query param with the current
request query params (payment=true), which is clearly wrong! The right
thing is to not manipulate the user provided `url` at all. If the user
want to append `payment=true` then they will have to change their ftd
code so that the `url` becomes "/experts/?id=120&payment=true".
@siddhantk232 siddhantk232 self-assigned this Sep 17, 2025
@siddhantk232 siddhantk232 requested a review from amitu September 17, 2025 10:02
@siddhantk232 siddhantk232 merged commit a473f41 into main Sep 17, 2025
1 check passed
@siddhantk232 siddhantk232 deleted the fix/http branch September 17, 2025 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants