entityMap|blocks|key|au68m|text|我遇到了同样的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|87im5|下面是我解决这个问题的方法：|fuvit|require+"woocommerce_api"

woocommerce+=+WooCommerce::API.new(
++"https://example.com",
++"consumer_key",
++"consumer_secret",
++{
++++wp_json:+true,
++++version:+"wc/v1",
++++query_string_auth:+true
++}
)|code-block|syntax|javascript|44sei|关键是|9c67o|下的查询字符串为true时，需要强制执行基本身份验证^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|N|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|O|9|@]|A|@]|B|$]]|$2|E|4|F|6|G|8|P|9|@]|A|@]|B|$H|I]]|$2|J|4|K|6|7|8|Q|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|R|9|@]|A|@]|B|$]]]]

I met same problem.

Here is how I solve it:

<pre><code>require "woocommerce_api"

woocommerce = WooCommerce::API.new(
 "https://example.com",
 "consumer_key",
 "consumer_secret",
 {
 wp_json: true,
 version: "wc/v1",
 query_string_auth: true
 }
)
</code></pre>

The key is <code>query_string_auth: true</code>
you need to force basic authentication as query string true under <code>HTTPS</code>

entityMap|blocks|key|7rre3|text|这就是我不再担心，继续前进的原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|77utj|简而言之，woocommerce的rest控制器几乎都有一个|dc65k|方法，该方法依次调用|an1ci|决定是否返回该错误；|fnsl2|所以你可以通过任何你想要的方式进行验证：|341m9|add_filter(+'woocommerce_rest_check_permissions',+'my_woocommerce_rest_check_permissions',+90,+4+);

function+my_woocommerce_rest_check_permissions(+$permission,+$context,+$object_id,+$post_type++){
++return+true;
}|code-block|syntax|javascript^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|Q|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|R|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|S|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|T|9|@]|A|@]|B|$]]|$2|K|4|L|6|M|8|U|9|@]|A|@]|B|$N|O]]]]

This is how i stopped worrying and moved on. 

In short, the woocommerce rest controllers pretty much all have a <code>SOMEWPRESTCLASS::get_item_permissions_check()</code> method which in turn calls <code>wc_rest_check_post_permissions()</code> to decide if it returns that error; 

So you hook into that and validate whichever way you want:

<pre><code>add_filter( 'woocommerce_rest_check_permissions', 'my_woocommerce_rest_check_permissions', 90, 4 );

function my_woocommerce_rest_check_permissions( $permission, $context, $object_id, $post_type ){
 return true;
}
</code></pre>

entityMap|blocks|key|3k1rl|text|试图帮助他人:我在尝试卷曲时遇到了401响应，还有VBA试图以内容类型"application/json“的形式请求，然而，我能够通过在浏览器地址栏中输入以下内容来获取有效的响应：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|jc2g|https://mywebsite.com/wp-json/wc/v2/products?consumer|dn4jt|_|annh2|key=ck|6ksjt|fp9lj|胡言乱语&消费者|4m7rq|7llgc|secret=cs|5q49n|e7j7j|胡言乱语|41q5l|按照这个思路，我返回到我的VBA应用程序，将内容类型更改为"application/+text“，并能够提取响应代码为200的有效响应文本。希望这对某些人有帮助。^0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|T|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|U|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|V|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|W|9|@]|A|@]|B|$]]|$2|I|4|F|6|7|8|X|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|Y|9|@]|A|@]|B|$]]|$2|L|4|F|6|7|8|Z|9|@]|A|@]|B|$]]|$2|M|4|N|6|7|8|10|9|@]|A|@]|B|$]]|$2|O|4|F|6|7|8|11|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|12|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|13|9|@]|A|@]|B|$]]]]

Trying to help others:
I was struggling with the 401 response while trying to CURL, and also with VBA trying to request as content-type "application/json"
However, I was able to pull a valid response by just entering this in my browser address bar:
<a href="https://mywebsite.com/wp-json/wc/v2/products?consumer_key=ck_blahblah&amp;consumer_secret=cs_blahblah" rel="nofollow noreferrer">https://mywebsite.com/wp-json/wc/v2/products?consumer_key=ck_blahblah&amp;consumer_secret=cs_blahblah</a>

Following this line of thought, I went back to my VBA app and changed the content type to "application/text" and was able to pull a valid response text with response code 200. 
Hope this helps someone.

entityMap|blocks|key|b9nc6|text|尝试一下，我在automattic/woocommerce库中遇到了同样的问题，我只是通过添加客户来让它正常工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|f2g5c|_|qgpk|密钥和客户|5qu8a|f8b6n|查询的秘密。|hinl|$woocommerce->get("customers/$userId?consumer_key={$this->key}&consumer_secret={$this->secret}");|code-block|syntax|javascript|6blur|快速编辑|9k35a|上面的方法可以工作，但我为automattic/woocommerce库找到了一个更好的解决方案。|32rbl|设置|fictk|查询|2gp0b|6sd1l|字符串|aeb5q|1o8h4|身份验证|eglm7|至|62t8p|正确|1j7jj|我必须深入研究代码才能找到这个设置。|3rugj|在文档里什么也没找到|c51ro|return+new+Client($this->url,+$this->key,+$this->secret,+[
++++"query_string_auth"+=>+true
]);^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|1C|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|1D|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|1E|9|@]|A|@]|B|$]]|$2|G|4|D|6|7|8|1F|9|@]|A|@]|B|$]]|$2|H|4|I|6|7|8|1G|9|@]|A|@]|B|$]]|$2|J|4|K|6|L|8|1H|9|@]|A|@]|B|$M|N]]|$2|O|4|P|6|7|8|1I|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|1J|9|@]|A|@]|B|$]]|$2|S|4|T|6|7|8|1K|9|@]|A|@]|B|$]]|$2|U|4|V|6|7|8|1L|9|@]|A|@]|B|$]]|$2|W|4|D|6|7|8|1M|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1N|9|@]|A|@]|B|$]]|$2|Z|4|D|6|7|8|1O|9|@]|A|@]|B|$]]|$2|10|4|11|6|7|8|1P|9|@]|A|@]|B|$]]|$2|12|4|13|6|7|8|1Q|9|@]|A|@]|B|$]]|$2|14|4|15|6|7|8|1R|9|@]|A|@]|B|$]]|$2|16|4|17|6|7|8|1S|9|@]|A|@]|B|$]]|$2|18|4|19|6|7|8|1T|9|@]|A|@]|B|$]]|$2|1A|4|1B|6|L|8|1U|9|@]|A|@]|B|$M|N]]]]

Try this, I had the same issue with the automattic/woocommerce library and I just got it working by appending the customer_key and customer_secret to the query.

<pre><code>$woocommerce-&gt;get("customers/$userId?consumer_key={$this-&gt;key}&amp;consumer_secret={$this-&gt;secret}");
</code></pre>

<hr>

Quick Edit

<hr>

The above method works but I found a better solution for the automattic/woocommerce library.

Set query_string_auth to true

Had to dig into the code to find this setting. 

Found nothing on it in the docs

<pre><code>return new Client($this-&gt;url, $this-&gt;key, $this-&gt;secret, [
 "query_string_auth" =&gt; true
]);
</code></pre>

entityMap|blocks|key|bksnf|text|你收到的401错误是因为你正在使用基本认证，即使你的网站不安全(没有https)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|7g6oo|postman中的解决方案是使用OAuth+1.0。只需添加消费者密钥和消费者机密并发送请求即可。^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|E|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|F|9|@]|A|@]|B|$]]]]

The 401 error you are getting is because you are using basic auth even though your website is not secure (does not have https).

The solution in postman is to use OAuth 1.0. Just add the consumer key and consumer secret and send the request.

entityMap|blocks|key|dqqdj|text|我就是碰到了这个。显然，curl处理url的方式有些可笑，所以我不得不把它封装在双引号中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|500ap|这不起作用:+curl|3r89g|https://www.my-site.com/wp-json/wc/v3/orders?consumer|94q60|_|ft0li|key=ck|20mu|dtl1o|40097dbc2844ce7712e1820bcadf0149c2bedegh&consumer|eh692|2picd|secret=cs|2qc1n|99t1f|ab57e19263af0b9ab4c596c310f1e7904bb20123|2gq1j|这是可行的:+curl|9bip2|“|9190l|9lna2|9vkmi|deer7|9adb7|e8ffh|f8stb|6v6fh|eg070|erjs2^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|17|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|18|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|19|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|1A|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|1B|9|@]|A|@]|B|$]]|$2|K|4|H|6|7|8|1C|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|1D|9|@]|A|@]|B|$]]|$2|N|4|H|6|7|8|1E|9|@]|A|@]|B|$]]|$2|O|4|P|6|7|8|1F|9|@]|A|@]|B|$]]|$2|Q|4|H|6|7|8|1G|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|1H|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|1I|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1J|9|@]|A|@]|B|$]]|$2|X|4|F|6|7|8|1K|9|@]|A|@]|B|$]]|$2|Y|4|H|6|7|8|1L|9|@]|A|@]|B|$]]|$2|Z|4|J|6|7|8|1M|9|@]|A|@]|B|$]]|$2|10|4|H|6|7|8|1N|9|@]|A|@]|B|$]]|$2|11|4|M|6|7|8|1O|9|@]|A|@]|B|$]]|$2|12|4|H|6|7|8|1P|9|@]|A|@]|B|$]]|$2|13|4|P|6|7|8|1Q|9|@]|A|@]|B|$]]|$2|14|4|H|6|7|8|1R|9|@]|A|@]|B|$]]|$2|15|4|S|6|7|8|1S|9|@]|A|@]|B|$]]|$2|16|4|W|6|7|8|1T|9|@]|A|@]|B|$]]]]

I just ran into this. Apparently something was funny with how curl was handling the url, so I had to encapsulate it in double quotes.

This doesn't work:
curl <a href="https://www.my-site.com/wp-json/wc/v3/orders?consumer_key=ck_40097dbc2844ce7712e1820bcadf0149c2bedegh&amp;consumer_secret=cs_ab57e19263af0b9ab4c596c310f1e7904bb20123" rel="nofollow noreferrer">https://www.my-site.com/wp-json/wc/v3/orders?consumer_key=ck_40097dbc2844ce7712e1820bcadf0149c2bedegh&amp;consumer_secret=cs_ab57e19263af0b9ab4c596c310f1e7904bb20123</a>

This does work:
curl "<a href="https://www.my-site.com/wp-json/wc/v3/orders?consumer_key=ck_40097dbc2844ce7712e1820bcadf0149c2bedegh&amp;consumer_secret=cs_ab57e19263af0b9ab4c596c310f1e7904bb20123" rel="nofollow noreferrer">https://www.my-site.com/wp-json/wc/v3/orders?consumer_key=ck_40097dbc2844ce7712e1820bcadf0149c2bedegh&amp;consumer_secret=cs_ab57e19263af0b9ab4c596c310f1e7904bb20123</a>"

entityMap|blocks|key|es3hv|text|以下是对Quickredfox答案的修改：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|f8066|add_filter('woocommerce_rest_check_permissions',+'my_woocommerce_rest_check_permissions',+90,+4);

function+my_woocommerce_rest_check_permissions($permission,+$context,+$object_id,+$post_type)+{
++++if($_GET['consumer_key']+==+'asdfghj'+&&+$_GET['consumer_secret']+==+'qwerty')+{
++++++++return+true;
++++}

++++return+$permission;
}|code-block|syntax|javascript|87cag|这样做的缺点是失去了为使用gui的用户添加和撤销访问的灵活性。但是，如果其他方法都不起作用，而且你就是找不出原因，那么这个方法就会起作用，而且不会将API公开给全世界。|cta3p|哦，这需要将key和secret作为参数进行传递：|aejm3|https://foo.bar.com/wp-json/wc/v3/products/123&consumer_key=asdfghj&consumer_secret=qwerty|d65c7|这将在没有https的情况下工作，但如果您在没有https的情况下使用它，请记住，随请求一起发送的任何凭据都将以纯文本形式发送。^0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|P|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|Q|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|R|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|S|9|@]|A|@]|B|$]]|$2|L|4|M|6|E|8|T|9|@]|A|@]|B|$F|G]]|$2|N|4|O|6|7|8|U|9|@]|A|@]|B|$]]]]

Here is a modified answer to Quickredfox's anwer:

<pre><code>add_filter('woocommerce_rest_check_permissions', 'my_woocommerce_rest_check_permissions', 90, 4);

function my_woocommerce_rest_check_permissions($permission, $context, $object_id, $post_type) {
 if($_GET['consumer_key'] == 'asdfghj' &amp;&amp; $_GET['consumer_secret'] == 'qwerty') {
 return true;
 }

 return $permission;
}
</code></pre>

The downside to this is that the flexibility of adding and revoking access for users using a gui is lost. However, if nothing else works and you just can't figure out why, this will work and does not expose the API to the whole world. 

Oh, and this requires passing the key and secret as parameters a la:

<pre><code>https://foo.bar.com/wp-json/wc/v3/products/123&amp;consumer_key=asdfghj&amp;consumer_secret=qwerty
</code></pre>

This will work without https, but if you use it without https, remember that any credentials you send along with your request will be sent in plain text.

entityMap|blocks|key|d9to2|text|对于本地开发(localhost)，您也可以使用Basic+Auth+(例如，对于Postman)，而不是Consumer+Key+&+Consumer+Secret。它可以无缝地工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data^0^^$0|$]|1|@$2|3|4|5|6|7|8|C|9|@]|A|@]|B|$]]]]

For local development (localhost) you can also use Basic Auth (e.g. for Postman) instead of Consumer Key &amp; Consumer Secret. It works seamlessly.

entityMap|0|type|IMAGE|mutability|IMMUTABLE|data|imageUrl|https://ask.qcloudimg.com/http-save/actteam/98f0c3cb1463da2975d81f9814a6fb2e.png|imageAlt|blocks|key|befk5|text|您可以使用postman尝试Oauth+1.0：|unstyled|depth|inlineStyleRanges|entityRanges|2klid|​|air3d|8d9p2|?|atomic|offset|length|2il6d|cka5o^0|0|0|0|0|1|0|0|0^^$0|$1|$2|3|4|5|6|$7|8|9|-4]]]|A|@$B|C|D|E|2|F|G|T|H|@]|I|@]|6|$]]|$B|J|D|K|2|F|G|U|H|@]|I|@]|6|$]]|$B|L|D|-4|2|F|G|V|H|@]|I|@]|6|$]]|$B|M|D|N|2|O|G|W|H|@]|I|@$P|X|Q|Y|B|Z]]|6|$]]|$B|R|D|-4|2|F|G|10|H|@]|I|@]|6|$]]|$B|S|D|K|2|F|G|11|H|@]|I|@]|6|$]]]]

You can try Oauth 1.0 with postman:

<a href="https://i.stack.imgur.com/6BRW9.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/6BRW9.png" alt="here is screenshot"></a>

entityMap|blocks|key|3j2nd|text|尝试使用查询参数发出请求，如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|c8emb|https://www.exemple.com/wp-json/wc/v3/orders?consumer_key=ck_01234567890&consumer_secret=cs_01234567890|code-block|syntax|javascript|5ar3n|这里：|8utk6|你需要填写你的url域。|95tbh|这里|eohoi|：|3d69t|是您的|3o1fl|确认|98scu|和|5d9f1|cs|clgi|这是上一代的|8j3gq|WooCommerce+>设置>高级>+REST+API^0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|11|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|12|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|13|9|@]|A|@]|B|$]]|$2|J|4|K|6|7|8|14|9|@]|A|@]|B|$]]|$2|L|4|M|6|7|8|15|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|16|9|@]|A|@]|B|$]]|$2|P|4|Q|6|7|8|17|9|@]|A|@]|B|$]]|$2|R|4|S|6|7|8|18|9|@]|A|@]|B|$]]|$2|T|4|U|6|7|8|19|9|@]|A|@]|B|$]]|$2|V|4|W|6|7|8|1A|9|@]|A|@]|B|$]]|$2|X|4|Y|6|7|8|1B|9|@]|A|@]|B|$]]|$2|Z|4|10|6|7|8|1C|9|@]|A|@]|B|$]]]]

Try making the request using query parameter, like this:
<pre><code>https://www.exemple.com/wp-json/wc/v3/orders?consumer_key=ck_01234567890&amp;consumer_secret=cs_01234567890
</code></pre>
here: <code>https://www.exemple.com</code> you'll need to fill your url domain.
here: <code>consumer_key and consumer_secret</code> is your ck and cs that was previous genereted on WooCommerce &gt; Settings &gt; Advanced &gt; REST API

entityMap|blocks|key|8jotq|text|我刚刚遇到了这个问题，我得到的错误信息与OP完全相同。我使用的是https和OAuth+1，问题出在域名上。我试着访问|type|unstyled|depth|inlineStyleRanges|entityRanges|data|643rk|站点的正确域名是|c8lti|..。|lruf|此URL返回401+woocommerce|ej6eu|_|cdr1i|休息|8q5c5|d9k5m|不能|7pgua|92jme|查看错误：|cdb6t|https://example.com/wp-json/wc/v3/products|code-block|syntax|javascript|9kmcn|此URL工作并返回结果：|ebksd|https://www.example.com/wp-json/wc/v3/products^0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|11|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|12|9|@]|A|@]|B|$]]|$2|E|4|F|6|7|8|13|9|@]|A|@]|B|$]]|$2|G|4|H|6|7|8|14|9|@]|A|@]|B|$]]|$2|I|4|J|6|7|8|15|9|@]|A|@]|B|$]]|$2|K|4|L|6|7|8|16|9|@]|A|@]|B|$]]|$2|M|4|J|6|7|8|17|9|@]|A|@]|B|$]]|$2|N|4|O|6|7|8|18|9|@]|A|@]|B|$]]|$2|P|4|J|6|7|8|19|9|@]|A|@]|B|$]]|$2|Q|4|R|6|7|8|1A|9|@]|A|@]|B|$]]|$2|S|4|T|6|U|8|1B|9|@]|A|@]|B|$V|W]]|$2|X|4|Y|6|7|8|1C|9|@]|A|@]|B|$]]|$2|Z|4|10|6|U|8|1D|9|@]|A|@]|B|$V|W]]]]

I just ran into this, I was getting the exact same error message as OP. I was using https and OAuth 1. The problem ended up being the domain. I was trying to access <code>example.com</code> when the correct domain for the site was <code>www.example.com</code>.
This URL returns 401 woocommerce_rest_cannot_view error:
<pre><code>https://example.com/wp-json/wc/v3/products
</code></pre>
This URL works and returns results:
<pre><code>https://www.example.com/wp-json/wc/v3/products
</code></pre>

entityMap|blocks|key|8f0ce|text|将此代码添加到function.php以解决此问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1mu3b|add_filter(+'woocommerce_rest_check_permissions',+'my_woocommerce_rest_check_permissions',+90,+4+);

function+my_woocommerce_rest_check_permissions(+$permission,+$context,+$object_id,+$post_type++){
++return+true;
}|code-block|syntax|javascript^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|I|9|@]|A|@]|B|$F|G]]]]

Add this code to function.php to fix the problem:
<pre><code>add_filter( 'woocommerce_rest_check_permissions', 'my_woocommerce_rest_check_permissions', 90, 4 );

function my_woocommerce_rest_check_permissions( $permission, $context, $object_id, $post_type ){
 return true;
}
</code></pre>

I have generated a consumer key and consumer secret. The website has SSL installed. I have also installed plugins required for JSON and REST services. This is how the url looks like:

<pre><code>https://&lt;url&gt;/wp-json/wc/v1/products
</code></pre>

When I am trying to get(GET) the product details using Basic Auth by using POSTMAN, a Chrome plugin, I get a JSON response like:

<pre><code>{
 "code": "woocommerce_rest_cannot_view",
 "message": "Sorry, you cannot list resources.",
 "data": {
 "status": 401
 }
}
</code></pre>

I have both the READ and WRITE permissions corresponding to the Consumer key.

WooCommerce - woocommerce_rest_cannot_view - Status 401

5位重磅专家聚焦 AI 时代开发者核心成长需求，带你深入解锁全栈进化、人机协作关键路径！点击报名到场：<a href="https://cloud.tencent.com/developer/salon/salon-2403/signup" target="_blank">https://cloud.tencent.com/developer/salon/salon-2403/signup</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/487c82639d2338df3ef66dfb1450601a.png"/>

腾讯技术创作特训营「年度论坛」正在报名中！

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

 我已经生成了一个消费者密钥和消费者机密。该网站已安装SSL。我还安装了JSON和REST服务所需的插件。这是url的样子： https:///wp-json/wc/v1/products 当我试图通过一个Chrome插件POSTMAN使用Basic Auth来获取(获取)产品的详细信息时，我得到了一个JSON响应，如...

问WooCommerce - woocommerce_rest_cannot_view -状态401
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问WooCommerce - woocommerce_rest_cannot_view -状态401EN