Repository navigation
docs: rift 0.23.0 behaviour — clearProxyResponses, StubRef.replace cycles, IPv4-mapped ip on dual-stack imposters - #336
Merged
Conversation
…nd ip predicates rift 0.23.0 changes three behaviours the SDK documents: clearProxyResponses also strips the responses proxyAlways appended to declared stubs and restarts every remaining stub's cycle (rift#1519); replacing a stub by index restarts its response cycle while by id keeps it (rift#1515); and a host-less imposter on an embedded or container engine listens dual-stack, recording an IPv4 client as ::ffff:127.0.0.1, so an ip predicate written as 127.0.0.1 stops matching there (rift#1514). The javadoc and recording docs now say so. Closes #331
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
rift 0.23.0 changes three behaviours that the SDK documents. These changes came out of the 0.23.0 impact survey.
Imposter.clearProxyResponses(rift#1519, PR compat(proxy): DELETE savedProxyResponses neither restarts surviving stubs' cycles nor strips proxyAlways-appended responses, as Mountebank's overwriteAll does rift#1542): it now also strips the responses that aproxyAlwaysproxy appended to stubs you declared, and it restarts the response cycle of every remaining stub, as Mountebank does.StubRef.replace(rift#1515, PR compat(stubs): PUT /imposters/:port/stubs/:index keeps the stub's response cursor; Mountebank resets the cycle rift#1538): replacing a stub addressed by index (the referenceaddStubreturns) restarts its response cycle, even when the content is unchanged. Replacing one addressed by id (stub(String)) keeps the cycle. This is in the javadoc and insdk-api.md.RequestField.IP/REQUEST_FROM(rift#1514, PR compat(imposter): an imposter with no host binds 0.0.0.0; Mountebank binds :: (dual-stack), so v4-wildcard conflicts and ::1 reachability differ rift#1536): a host-less imposter on an embedded engine or in aRiftContainernow listens dual-stack and records an IPv4 client as::ffff:127.0.0.1. Anippredicate written as127.0.0.1therefore no longer matches there;host("127.0.0.1")keeps the imposter IPv4. Spawned imposters bind--hostand are unaffected.docs/recording.md:proxyAlwaysresponses carry_proxyResponseTime, which round-trips throughIsResponse.extrawith no model change. The page also covers the newclearProxyResponsessemantics.Docs only, so there is no behaviour change. The javadoc builds cleanly.
Closes #331
🤖 Generated with Claude Code