I wanted to enrich my library contribution with pr...
# wiremock-clouds
Simon Verhoeven
10/12/2023, 5:48 PMI wanted to enrich my library contribution with proper payloads, but I seem to be missing something.
The API was imported fine => I click record => enter the actual API target URL => hit start => perform the apt curl => response of { }
I am basing myself upon: https://docs.wiremock.io/recording-stubs/#:~:text=Once%20you%20have%20logged%20into,the%20target%20URL%20and%20hit%20.&text=This%20request%20will%20be%20proxied,json%20and%20the%20result%20captured.
t
Tom
10/12/2023, 6:53 PMStrange, it worked as expected for me
Tom
10/12/2023, 6:54 PMI wonder if the target API just happened to give a spurious response when you were recording?
s
Simon Verhoeven
10/12/2023, 6:56 PMOdd, I just tried again with the same results.
t
Tom
10/12/2023, 6:57 PMSame bad result?
Tom
10/12/2023, 6:58 PMCould you try with
-vs
Simon Verhoeven
10/12/2023, 6:59 PMverho@home-pc MINGW64 /c/Development/api-template-library (foojay-discoapi-template)
$ curl https://3lg1y.wiremockapi.cloud/disco/v3.0/supported_terms_of_support -v
* Trying 44.204.248.166:443...
* Connected to 3lg1y.wiremockapi.cloud (44.204.248.166) port 443 (#0)
* schannel: disabled automatic use of client certificate
* using HTTP/1.x
GET /disco/v3.0/supported_terms_of_support HTTP/1.1
Host: 3lg1y.wiremockapi.cloud
User-Agent: curl/8.1.2
Accept: /* schannel: remote party requests renegotiation * schannel: renegotiating SSL/TLS connection * schannel: SSL/TLS connection renegotiated * schannel: remote party requests renegotiation * schannel: renegotiating SSL/TLS connection * schannel: SSL/TLS connection renegotiated * schannel: remote party requests renegotiation * schannel: renegotiating SSL/TLS connection * schannel: SSL/TLS connection renegotiated < HTTP/1.1 200 OK < Vary: Origin < Content-Type: application/json < Matched-Stub-Id: dda0378b-5faf-468c-a656-891139bbf52c < Matched-Stub-Name: Returns the supported terms of support < Content-Length: 3 < { }* Connection #0 to host 3lg1y.wiremockapi.cloud left intact
t
Tom
10/12/2023, 7:00 PMAh, you have a stub that already matches that request and it’s serving that as a response
Tom
10/12/2023, 7:00 PMIf you delete the stub named “Returns the supported terms of support” then try again it should work
s
Simon Verhoeven
10/12/2023, 7:04 PMAh ok, thank you. I thought it would update the existing ones if it already matched.
t
Tom
10/12/2023, 7:04 PMNo, it won’t touch existing stubs at the moment.
s
Simon Verhoeven
10/12/2023, 7:19 PMt
Tom
10/12/2023, 7:20 PMWhat triggered that?
s
Simon Verhoeven
10/12/2023, 7:20 PMI did a couple of recordings in a row
Simon Verhoeven
10/12/2023, 7:20 PMAnd some are seemingly missing
Simon Verhoeven
10/12/2023, 7:20 PMThe UI seemingly does not also like it: https://app.wiremock.cloud/mock-apis/m63vv/stubs/f791c4c2-1395-40f9-8183-14b091c2801c
Simon Verhoeven
10/12/2023, 7:21 PMthere are some pretty large payloads in there
t
Tom
10/12/2023, 7:21 PMI can’t follow that link unfortunately. Could you send a screenshot of the UI error?
s
Simon Verhoeven
10/12/2023, 7:22 PMit recovers after a while, just very sluggish
t
Tom
10/12/2023, 7:22 PMWe’re about to start some work to change the way we handle large response bodies
Tom
10/12/2023, 7:22 PMAt the moment it’s all in memory, inlined in the stub, and the UI component loads it all
s
Simon Verhoeven
10/12/2023, 7:22 PMThat's what I assumed
t
Tom
10/12/2023, 7:23 PMWe’re going to set a threshold above which it uses file uploads/downloads
s
Simon Verhoeven
10/12/2023, 7:23 PMI was documenting https://api.foojay.io/swagger-ui#/ to improve my library PR
👍 1
t
Tom
10/12/2023, 7:24 PMIs there a URL you can share with me that I can use for my own testing?
Tom
10/12/2023, 7:24 PMWould be useful to replicate what you’re seeing so that we can use it to improve things in the interim
s
Simon Verhoeven
10/12/2023, 7:26 PMt
Tom
10/12/2023, 8:06 PMThanks, please leave this with me
Tom
10/12/2023, 8:10 PMYeah, 25MB payload. Think we’re not quite up to that at the moment.
2 Views