blocks|key|1834408|text|目前，规则没有禁用属性。您可以删除一个wiremock规则，并在以后重新添加它，这在功能上是相同的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1834409|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

There presently isn't a disable attribute to a rule. You can remove a wiremock rule and re-add it later, which would functionally be the same.

blocks|key|598725|text|您可以使用WireMock管理界面禁用规则。如果对http://.../__admin/mappings/<guid>调用DELETE命令，则映射将被删除。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|598726|通过对http://.../__admin/执行get命令，可以获得所有guids的列表|598727|如果您想用一个真正的响应来代替一个映射，而不是一个存根响应，那么您可以添加第二个映射，它的优先级低于存根响应，并且该代理可以一直到真实的地址。通常，您的存根响应不会被使用，但是当您删除短消息响应时，Wiremock将代理到真正的地址，因为它将成为最高优先级的映射。|598728|要添加代理，请将以下内容添加到响应映射中|598729|"proxyBaseUrl"+:+"http://otherhost.com",|598730|要设置映射的优先级，请将以下内容添加到映射JSON中。|598731|"priority":+1,|598732|entityMap^0|P|Y|0|3|J|0|0|0|0|14|0|0|0|E|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|N|3|O|5|6|7|14|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|S|$]]

You can disable a rule by using the WireMock admin interface. If you invoke a DELETE command against <code>http://.../__admin/mappings/&lt;guid&gt;</code>, then the mapping will be deleted.

You can get a list of all the guids by performing a GET command against <code>http://.../__admin/</code>

If you want to replace a mapping with a real response instead of a stubbed response, you can add a second mapping that has a lower priority than the stubbed response and that proxies through to the real address. Normally, your stubbed response ill be used, but when you then delete the stubbed response, Wiremock will proxy through to the real address as it will then become the highest priority mapping.

To add a proxy, add the following into the response mapping

<code>"proxyBaseUrl" : "http://otherhost.com",</code>

To set the priority of mappings, add the following into your mapping JSON.

<code>"priority": 1,</code>

blocks|key|1834514|text|如果您将Wiremock作为流程运行，则可以将其设置为记录方式，这将有效地将所有请求代理到目标URL。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1834515|打开管理员/记录器+(假设您在默认端口8080上启动了WireMock+)，在该屏幕上您必须输入目标URL并单击"Record“按钮。除非你停止录音，否则它会让这个威瑞克充当代理。|1834516|如果记录不是您实际需要的东西，则可以取消记录存根映射。虽然这稍微滥用了Recorder特性，但这是一种快速而简单的方法，可以暂时将您的Wiremock转换为代理，而不是使用存根进行响应。|1834517|entityMap|0|LINK|mutability|MUTABLE|url|http://wiremock.org/docs/running-standalone/|1|http://wiremock.org/docs/record-playback/|2|http://localhost:8080/__admin/recorder^0|E|2|0|R|4|1|0|2|7|2|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]|$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

If you running Wiremock as a <a href="http://wiremock.org/docs/running-standalone/" rel="nofollow noreferrer">Stand-alone process</a>, you can set it into <a href="http://wiremock.org/docs/record-playback/" rel="nofollow noreferrer">recording mode</a>, effectively this will proxy all requests to a target URL.
Open <a href="http://localhost:8080/__admin/recorder" rel="nofollow noreferrer">http://localhost:8080/__admin/recorder</a> (assuming you started WireMock on the default port of 8080), on that screen you have to enter the target URL and click the &quot;Record&quot; button. Until you stop recording it will make this Wiremock acting as a proxy.
If the recording is not something you actually need, you can dismiss recorded stub mappings. Although this is slightly misusing the Recorder feature it is a fast and easy way to temporarily turn your Wiremock into a proxy, instead of responding with stubs.

blocks|key|598822|text|Wiremock可以根据运行在哪个情景的状态中选择要使用的夹具。在不同的状态下，即使对于相同的请求，它也可能有不同的映射，因此表现出不同的方式(其中一种状态可以从一个夹具中响应，而在另一种状态下，它可以被转发到真正的API)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|598823|如果有代理场景，目前处于默认启动状态，那么所有查询都将由不特定于任何场景状态的存根提供服务。|598824|但是，如果代理场景处于活动状态，并且我们有一个特定于该场景状态的映射(requiredScenarioState属性)，并且它具有比默认更高的优先级，那么这个映射将被执行到这个Wiremock实例的任何URI：|598825|{
++++"scenarioName":+"Proxy",
++++"requiredScenarioState":+"Activated",
++++"priority":+2,
++++"request":+{
++++++++"urlPattern":+".*"
++++},
++++"response":+{
++++++++"proxyBaseUrl":+"https://swapi.dev/api"
++++}
}|code-block|syntax|javascript|598826|当匹配此映射时，response.proxyBaseUrl的值将发出所有要转发给提供主机的请求。|598827|现在，我们需要能够将代理场景切换到激活的状态和回退，因此我们在这个Wiremock上为POST+/proxy端点定义了另外两个映射。它们将具有更高的优先级-+1，因此它们甚至可以覆盖"urlPattern":+".*"的映射。|style|CODE|598828|删除包含到wiremock/mappings的所有三个映射的JSON文件|598829|{
++++"mappings":+[
++++++++{
++++++++++++"scenarioName":+"Proxy",
++++++++++++"requiredScenarioState":+"Activated",
++++++++++++"priority":+2,
++++++++++++"request":+{
++++++++++++++++"urlPattern":+".*"
++++++++++++},
++++++++++++"response":+{
++++++++++++++++"proxyBaseUrl":+"https://swapi.dev/api"
++++++++++++}
++++++++},
++++++++{
++++++++++++"priority":+1,
++++++++++++"scenarioName":+"Proxy",
++++++++++++"requiredScenarioState":+"Activated",
++++++++++++"newScenarioState":+"Started",
++++++++++++"request":+{+"method":+"POST",+"url":+"/proxy"},
++++++++++++"response":+{+"status":+201,+"body":+"Proxy+De-activated+(Stubs+will+be+used)"+}
++++++++},
++++++++{
++++++++++++"priority":+1,
++++++++++++"scenarioName":+"Proxy",
++++++++++++"requiredScenarioState":+"Started",
++++++++++++"newScenarioState":+"Activated",
++++++++++++"request":+{+"method":+"POST",+"url":+"/proxy"+},
++++++++++++"response":+{+"status":+201,+"body":+"Proxy+Activated+(Will+forward+all+requests)"+}
++++++++}
++++]
}|598830|现在，您可以将代理场景切换到激活状态，并在将其切换回已启动状态之后：|598831|curl+http://localhost:8080/proxy+-XPOST|598832|这种方法的好处是，这个映射文件可以以最小的更改从一个项目复制到另一个项目。|598833|entityMap|0|LINK|mutability|MUTABLE|url|http://wiremock.org/docs/stateful-behaviour/^0|H|5|0|0|0|0|0|0|17|B|2J|I|0|5|H|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|1F|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1G|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1H|8|@]|9|@]|C|$]]|$1|O|3|P|5|6|7|1I|8|@$A|1J|B|1K|Q|R]|$A|1L|B|1M|Q|R]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1N|8|@$A|1O|B|1P|Q|R]]|9|@]|C|$]]|$1|U|3|V|5|J|7|1Q|8|@]|9|@]|C|$K|L]]|$1|W|3|X|5|6|7|1R|8|@]|9|@]|C|$]]|$1|Y|3|Z|5|J|7|1S|8|@]|9|@]|C|$K|L]]|$1|10|3|11|5|6|7|1T|8|@]|9|@]|C|$]]|$1|12|3|-4|5|6|7|1U|8|@]|9|@]|C|$]]]|13|$14|$5|15|16|17|C|$18|19]]]]

Wiremock can select which fixture to use depending on in which <a href="http://wiremock.org/docs/stateful-behaviour/" rel="nofollow noreferrer">state of a scenario</a> it runs. In different states, even for same request, it can have different mappings thus behave in different ways (in one of the states can respond from a fixture, and in another state it can be forwarded to the real API).
Say if there is a Proxy scenario, which is currently in the default Started state, then all the queries will be served by stubs that are not specific to any scenario state.
But if the Proxy scenario is in Active state, and we have a mapping that is specific for that scenario state (requiredScenarioState property), and it has a higher priority than default, then this mapping will be executed for any URI to this Wiremock instance:
<pre><code>{
 &quot;scenarioName&quot;: &quot;Proxy&quot;,
 &quot;requiredScenarioState&quot;: &quot;Activated&quot;,
 &quot;priority&quot;: 2,
 &quot;request&quot;: {
 &quot;urlPattern&quot;: &quot;.*&quot;
 },
 &quot;response&quot;: {
 &quot;proxyBaseUrl&quot;: &quot;https://swapi.dev/api&quot;
 }
}
</code></pre>
The value for response.proxyBaseUrl, will make all the requests to be forwarded to provided host, when this mapping is matched.
Now we need to be able to toggle Proxy scenario to Activated state and back,
so we define two more mappings for <code>POST /proxy</code> endpoint on this Wiremock. They will have even higher priority - 1, so they can override even the mapping for <code>&quot;urlPattern&quot;: &quot;.*&quot;</code>.
Drop a JSON file containing all three mappings to your <code>wiremock/mappings</code>:
<pre><code>{
 &quot;mappings&quot;: [
 {
 &quot;scenarioName&quot;: &quot;Proxy&quot;,
 &quot;requiredScenarioState&quot;: &quot;Activated&quot;,
 &quot;priority&quot;: 2,
 &quot;request&quot;: {
 &quot;urlPattern&quot;: &quot;.*&quot;
 },
 &quot;response&quot;: {
 &quot;proxyBaseUrl&quot;: &quot;https://swapi.dev/api&quot;
 }
 },
 {
 &quot;priority&quot;: 1,
 &quot;scenarioName&quot;: &quot;Proxy&quot;,
 &quot;requiredScenarioState&quot;: &quot;Activated&quot;,
 &quot;newScenarioState&quot;: &quot;Started&quot;,
 &quot;request&quot;: { &quot;method&quot;: &quot;POST&quot;, &quot;url&quot;: &quot;/proxy&quot;},
 &quot;response&quot;: { &quot;status&quot;: 201, &quot;body&quot;: &quot;Proxy De-activated (Stubs will be used)&quot; }
 },
 {
 &quot;priority&quot;: 1,
 &quot;scenarioName&quot;: &quot;Proxy&quot;,
 &quot;requiredScenarioState&quot;: &quot;Started&quot;,
 &quot;newScenarioState&quot;: &quot;Activated&quot;,
 &quot;request&quot;: { &quot;method&quot;: &quot;POST&quot;, &quot;url&quot;: &quot;/proxy&quot; },
 &quot;response&quot;: { &quot;status&quot;: 201, &quot;body&quot;: &quot;Proxy Activated (Will forward all requests)&quot; }
 }
 ]
}
</code></pre>
Now you can switch the Proxy scenario to Activated state,
and after switch it back to Started state with:
<pre><code>curl http://localhost:8080/proxy -XPOST
</code></pre>
Good thing about this approach that this mapping file can be copied from project to project with minimal changes.

I use WireMock to stub responses from remote server.
In folder <code>wiremock/mappings</code> I have many files that set rules for stub.
Here example:

{

<pre><code> "request": {
 "method": "GET",
 "url": "/merchant"
 },
 "response": {
 "headers": {
 "Content-Type": "application/json"
 },
 "status": 200,
 "fixedDelayMilliseconds": 3000,
 "bodyFileName": "stub_response.json"
 }
}
</code></pre>

As you can see, when I get request <code>/merchant</code> then return stubbed response from file <code>stub_response.json</code>.
Nice. It's work fine.

But suppose I need temporary to disable this response. Is it possible to turn off stub response and return real response from remote server?

I need flag like this : <code>"disable" : true</code>

Is it possible in WireMock?

WireMock: Temp disable stub response

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我使用WireMock从远程服务器进行存根响应。在文件夹wiremock/mappings中，我有许多设置存根规则的文件。这里的例子是：{  "request": {    "method": "GET",    "url": "/merchant"  },  "response": {    "headers": {...

问WireMock:临时禁用存根响应
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WireMock:临时禁用存根响应EN