[GH-ISSUE #370] Repeat doesn't preserve query items #366

Closed
opened 2026-03-03 19:17:51 +03:00 by kerem · 8 comments
Owner

Originally created by @cameroncooke on GitHub (Jan 9, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/370

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? (Ex. Proxyman 1.4.3)

1.13.1

macOS Version? (Ex. mac 10.14)

10.15.3 Beta (19D49f)

Steps to reproduce

Repeat a request which has query items.

Expected behavior

Repeated request should have identical payload and query string as original.

Originally created by @cameroncooke on GitHub (Jan 9, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/370 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? (Ex. Proxyman 1.4.3) `1.13.1` ### macOS Version? (Ex. mac 10.14) 10.15.3 Beta (19D49f) ### Steps to reproduce Repeat a request which has query items. ### Expected behavior Repeated request should have identical payload and query string as original.
kerem 2026-03-03 19:17:51 +03:00
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 10, 2020):

Hi @cameroncooke, so far from what I testing with complex Query item and the repeated request:

  • They are the same Query item
  • Has additionally Header key (Alamofire adds)
  • Same Response
    => It's correct behavior

I'm not sure how can I reproduce your case. Can you give me an example how the Query look like that cause the bug? 🤔

<!-- gh-comment-id:572850541 --> @NghiaTranUIT commented on GitHub (Jan 10, 2020): Hi @cameroncooke, so far from what I testing with complex Query item and the repeated request: - They are the same Query item - Has additionally Header key (Alamofire adds) - Same Response => It's correct behavior I'm not sure how can I reproduce your case. Can you give me an example how the Query look like that cause the bug? 🤔
Author
Owner

@cameroncooke commented on GitHub (Jan 10, 2020):

I think I've narrowed down the issue, it seems to occur when repeating a
POST requests which have query items.
When repeating the query items are converted into form values i.e.
key/value pairs and are moved to the HTTP body and the Content-Type is
changed to application/x-www-form-urlencoded; charset=utf-8.

I would expect to repeat the request in an identical format. Also, query
items on POST requests are perfectly valid. If you're using Alamofire it
would appear it's conveniently or not conveniently trying to be cleaver and
rewrite the request. As a proxy tool for debugging, I would not expect my
requests to be changed in this way.

When testing with Charles it works as expected an identical request is
repeated.

Thanks.

Cameron.

On Fri, 10 Jan 2020 at 02:54, Nghia Tran notifications@github.com wrote:

Hi @cameroncooke https://github.com/cameroncooke, so far from what I
testing with complex Query item and the repeated request:

  • They are the same Query item
  • Has additionally Header key (Alamofire adds)
  • Same Response
    => It's correct behavior

I'm not sure how can I reproduce your case. Can you give me an example how
the Query look like that cause the bug? 🤔


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ProxymanApp/Proxyman/issues/370?email_source=notifications&email_token=AAEZ6SKIQ2CAPDE62EXWHT3Q47PPZA5CNFSM4KE22ZU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISQC3I#issuecomment-572850541,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEZ6SOCMRQRT3S556WGLWLQ47PPZANCNFSM4KE22ZUQ
.

<!-- gh-comment-id:572949695 --> @cameroncooke commented on GitHub (Jan 10, 2020): I think I've narrowed down the issue, it seems to occur when repeating a `POST` requests which have query items. When repeating the query items are converted into form values i.e. key/value pairs and are moved to the HTTP body and the `Content-Type` is changed to `application/x-www-form-urlencoded; charset=utf-8`. I would expect to repeat the request in an identical format. Also, query items on POST requests are perfectly valid. If you're using `Alamofire` it would appear it's conveniently or not conveniently trying to be cleaver and rewrite the request. As a proxy tool for debugging, I would not expect my requests to be changed in this way. When testing with Charles it works as expected an identical request is repeated. Thanks. Cameron. On Fri, 10 Jan 2020 at 02:54, Nghia Tran <notifications@github.com> wrote: > Hi @cameroncooke <https://github.com/cameroncooke>, so far from what I > testing with complex Query item and the repeated request: > > - They are the same Query item > - Has additionally Header key (Alamofire adds) > - Same Response > => It's correct behavior > > I'm not sure how can I reproduce your case. Can you give me an example how > the Query look like that cause the bug? 🤔 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/ProxymanApp/Proxyman/issues/370?email_source=notifications&email_token=AAEZ6SKIQ2CAPDE62EXWHT3Q47PPZA5CNFSM4KE22ZU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEISQC3I#issuecomment-572850541>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAEZ6SOCMRQRT3S556WGLWLQ47PPZANCNFSM4KE22ZUQ> > . >
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 10, 2020):

Thank for the valuable hint. I'm on it now 👍 Will send you a hot-fix build this weekend 🌮

<!-- gh-comment-id:573089221 --> @NghiaTranUIT commented on GitHub (Jan 10, 2020): Thank for the valuable hint. I'm on it now 👍 Will send you a hot-fix build this weekend 🌮
Author
Owner

@cameroncooke commented on GitHub (Jan 10, 2020):

Amazing thank you.

On 10 Jan 2020, at 15:46, Nghia Tran notifications@github.com wrote:


Thank for the valuable hint. I'm on it now 👍 Will send you a hot-fix build this weekend 🌮


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

<!-- gh-comment-id:573153033 --> @cameroncooke commented on GitHub (Jan 10, 2020): Amazing thank you. > On 10 Jan 2020, at 15:46, Nghia Tran <notifications@github.com> wrote: > >  > Thank for the valuable hint. I'm on it now 👍 Will send you a hot-fix build this weekend 🌮 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or unsubscribe.
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 13, 2020):

Hey @cameroncooke, here is the BETA build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.13.1_Repeat_Request_Bug.dmg

I will officially roll out in a next release 👍

<!-- gh-comment-id:573521331 --> @NghiaTranUIT commented on GitHub (Jan 13, 2020): Hey @cameroncooke, here is the BETA build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.13.1_Repeat_Request_Bug.dmg I will officially roll out in a next release 👍
Author
Owner

@cameroncooke commented on GitHub (Jan 13, 2020):

Hi Nghia, worked a treat, thanks so much for the quick fix.

Cameron.

On Mon, 13 Jan 2020 at 06:09, Nghia Tran notifications@github.com wrote:

Hey @cameroncooke https://github.com/cameroncooke, here is the BETA
build:
https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.13.1_Repeat_Request_Bug.dmg

I will officially roll out in a next release 👍


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ProxymanApp/Proxyman/issues/370?email_source=notifications&email_token=AAEZ6SOVTBG2WCNAMTF3OLLQ5QAR7A5CNFSM4KE22ZU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIXT3MY#issuecomment-573521331,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEZ6SL7LD7QYS4GOZFBYADQ5QAR7ANCNFSM4KE22ZUQ
.

<!-- gh-comment-id:573547611 --> @cameroncooke commented on GitHub (Jan 13, 2020): Hi Nghia, worked a treat, thanks so much for the quick fix. Cameron. On Mon, 13 Jan 2020 at 06:09, Nghia Tran <notifications@github.com> wrote: > Hey @cameroncooke <https://github.com/cameroncooke>, here is the BETA > build: > https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_1.13.1_Repeat_Request_Bug.dmg > > I will officially roll out in a next release 👍 > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/ProxymanApp/Proxyman/issues/370?email_source=notifications&email_token=AAEZ6SOVTBG2WCNAMTF3OLLQ5QAR7A5CNFSM4KE22ZU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIXT3MY#issuecomment-573521331>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAEZ6SL7LD7QYS4GOZFBYADQ5QAR7ANCNFSM4KE22ZUQ> > . >
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 14, 2020):

Glad to hear that 👍

<!-- gh-comment-id:573977274 --> @NghiaTranUIT commented on GitHub (Jan 14, 2020): Glad to hear that 👍
Author
Owner

@NghiaTranUIT commented on GitHub (Jan 21, 2020):

Just friendly reminder that Proxman 1.14.0 is released https://github.com/ProxymanApp/Proxyman/releases/tag/1.14.0.

Let update it 👍

<!-- gh-comment-id:576715079 --> @NghiaTranUIT commented on GitHub (Jan 21, 2020): Just friendly reminder that Proxman 1.14.0 is released https://github.com/ProxymanApp/Proxyman/releases/tag/1.14.0. Let update it 👍
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Proxyman#366
No description provided.