entityMap|blocks|key|1582666|text|替代方案1.|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1582667|设置您的.hosts+(Windows)或etc/hosts文件，将活动域指向您的本地主机IP。例如：|1582669|+127.0.0.1+xyz.com|blockquote|1582672|其中xyz.com是您的真实域名。|1582673|替代方案2.|1582674|此外，本文还给出了替代使用URL缩短服务的提示。缩短本地URL，并将结果作为回调提供。|1582675|替代方案3.|1582676|此外，它似乎可以提供例如http://127.0.0.1:8080作为Twitter的回调，而不是http://localhost:8080。|CODE|1582677^0|0|6|0|0|0|0|0|6|0|0|0|6|0|C|L|1D|L|0^^$0|$]|1|@$2|3|4|5|6|7|8|X|9|@$A|Y|B|Z|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|10|9|@]|E|@]|F|$]]|$2|I|4|J|6|K|8|11|9|@]|E|@]|F|$]]|$2|L|4|M|6|7|8|12|9|@]|E|@]|F|$]]|$2|N|4|O|6|7|8|13|9|@$A|14|B|15|C|D]]|E|@]|F|$]]|$2|P|4|Q|6|7|8|16|9|@]|E|@]|F|$]]|$2|R|4|S|6|7|8|17|9|@$A|18|B|19|C|D]]|E|@]|F|$]]|$2|T|4|U|6|7|8|1A|9|@$A|1B|B|1C|C|V]|$A|1D|B|1E|C|V]]|E|@]|F|$]]|$2|W|4|-4|6|7|8|1F|9|@]|E|@]|F|$]]]]

Alternative 1.

Set up your .hosts (Windows) or etc/hosts file to point a live domain to your localhost IP. such as:

<blockquote>
 127.0.0.1 xyz.com
</blockquote>

where xyz.com is your real domain.

Alternative 2.

Also, the article gives the tip to alternatively use a URL shortener service. Shorten your local URL and provide the result as callback.

Alternative 3.

Furthermore, it seems that it works to provide for example <code>http://127.0.0.1:8080</code> as callback to Twitter, instead of <code>http://localhost:8080</code>.

entityMap|blocks|key|5460033|text|我上个星期才不得不这么做。显然，localhost不能工作，但127.0.0.1能正常工作。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5460034|当然，这是假设你在Twitter上注册了两个应用，一个是为你的live+www.mysite.com注册的，另一个是为127.0.0.1注册的。|5460035^0|G|9|V|9|0|10|E|1N|9|0^^$0|$]|1|@$2|3|4|5|6|7|8|J|9|@$A|K|B|L|C|D]|$A|M|B|N|C|D]]|E|@]|F|$]]|$2|G|4|H|6|7|8|O|9|@$A|P|B|Q|C|D]|$A|R|B|S|C|D]]|E|@]|F|$]]|$2|I|4|-4|6|7|8|T|9|@]|E|@]|F|$]]]]

I just had to do this last week. Apparently <code>localhost</code> doesn't work but <code>127.0.0.1</code> does Go figure.

This of course assumes that you are registering two apps with Twitter, one for your live <code>www.mysite.com</code> and another for <code>127.0.0.1</code>.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://127.0.0.1:xxxx/|blocks|key|1931339|text|只需将http://127.0.0.1:xxxx/作为回调url，其中xxxx是框架的端口|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|1931340^0|3|M|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|L|G|@]|H|@$I|M|J|N|A|O]]|6|$]]|$A|K|C|-4|2|E|F|P|G|@]|H|@]|6|$]]]]

Just put <a href="http://127.0.0.1:xxxx/">http://127.0.0.1:xxxx/</a> as the callback url, where xxxx is the port for your framework

entityMap|blocks|key|1931164|text|是的，由于最近在OAuth中发现的安全问题，它被禁用。目前唯一的解决方案是创建两个OAuth应用程序-一个用于生产，另一个用于开发。在开发应用程序中，您设置本地主机回调URL，而不是活动的URL。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1931165^0|0^^$0|$]|1|@$2|3|4|5|6|7|8|D|9|@]|A|@]|B|$]]|$2|C|4|-4|6|7|8|E|9|@]|A|@]|B|$]]]]

Yes, it was disabled because of the recent security issue that was found in OAuth. The only solution for now is to create two OAuth applications - one for production and one for development. In the development application you set your localhost callback URL instead of the live one.

entityMap|blocks|key|1586994|text|回调URL已编辑|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1586995|http://localhost:8585/logintwitter.aspx|code-block|syntax|javascript|1586996|转换为|1586997|http://127.0.0.1:8585/logintwitter.aspx|1586998^0|0|0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@]|A|@]|B|$]]|$2|C|4|D|6|E|8|N|9|@]|A|@]|B|$F|G]]|$2|H|4|I|6|7|8|O|9|@]|A|@]|B|$]]|$2|J|4|K|6|E|8|P|9|@]|A|@]|B|$F|G]]|$2|L|4|-4|6|7|8|Q|9|@]|A|@]|B|$]]]]

Callback URL edited

<pre><code>http://localhost:8585/logintwitter.aspx
</code></pre>

Convert to

<pre><code>http://127.0.0.1:8585/logintwitter.aspx
</code></pre>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://127.0.0.1/Callback.aspx|blocks|key|5460057|text|我是这样做的：|unstyled|depth|inlineStyleRanges|entityRanges|5460058|注册回调地址：http://127.0.0.1/Callback.aspx|offset|length|5460059|+++OAuthTokenResponse+authorizationTokens+=+
++++++++OAuthUtility.GetRequestToken(ConfigSettings.getConsumerKey(),+
+++++++++++++++++++++++++++++++++++++ConfigSettings.getConsumerSecret(),+
+++++++++++++++++++++++++++++++++++++"http://127.0.0.1:1066/Twitter/Callback.aspx");|code-block|syntax|javascript|5460060|ConfigSettings：|5460061|public+static+class+ConfigSettings
{
++++public+static+String+getConsumerKey()
++++{
++++++++return+System.Configuration.ConfigurationManager.AppSettings["ConsumerKey"].ToString();
++++}

++++public+static+String+getConsumerSecret()
++++{
++++++++return+System.Configuration.ConfigurationManager.AppSettings["ConsumerSecret"].ToString();
++++}

}|5460062|Web.config：|5460063|<appSettings>

++++<add+key="ConsumerKey"+value="xxxxxxxxxxxxxxxxxxxx"/>
++++<add+key="ConsumerSecret"+value="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/>

</appSettings>|5460064|请确保将项目的属性“使用动态端口”设置为“false”，并输入静态端口号。(我使用了1066)。|5460065|我希望这能帮到你!|5460066^0|0|7|U|0|0|0|0|0|0|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|14|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|15|G|@]|H|@$K|16|L|17|A|18]]|6|$]]|$A|M|C|N|2|O|F|19|G|@]|H|@]|6|$P|Q]]|$A|R|C|S|2|E|F|1A|G|@]|H|@]|6|$]]|$A|T|C|U|2|O|F|1B|G|@]|H|@]|6|$P|Q]]|$A|V|C|W|2|E|F|1C|G|@]|H|@]|6|$]]|$A|X|C|Y|2|O|F|1D|G|@]|H|@]|6|$P|Q]]|$A|Z|C|10|2|E|F|1E|G|@]|H|@]|6|$]]|$A|11|C|12|2|E|F|1F|G|@]|H|@]|6|$]]|$A|13|C|-4|2|E|F|1G|G|@]|H|@]|6|$]]]]

This is how i did it: 

Registered Callback URL:
<a href="http://127.0.0.1/Callback.aspx" rel="noreferrer">http://127.0.0.1/Callback.aspx</a>

<pre><code> OAuthTokenResponse authorizationTokens = 
 OAuthUtility.GetRequestToken(ConfigSettings.getConsumerKey(), 
 ConfigSettings.getConsumerSecret(), 
 "http://127.0.0.1:1066/Twitter/Callback.aspx");
</code></pre>

ConfigSettings:

<pre><code>public static class ConfigSettings
{
 public static String getConsumerKey()
 {
 return System.Configuration.ConfigurationManager.AppSettings["ConsumerKey"].ToString();
 }

 public static String getConsumerSecret()
 {
 return System.Configuration.ConfigurationManager.AppSettings["ConsumerSecret"].ToString();
 }

}
</code></pre>

Web.config:

<pre><code>&lt;appSettings&gt;

 &lt;add key="ConsumerKey" value="xxxxxxxxxxxxxxxxxxxx"/&gt;
 &lt;add key="ConsumerSecret" value="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/&gt;

&lt;/appSettings&gt;
</code></pre>

Make sure you set the property 'use dynamic ports' of you project to 'false' and enter a static port number instead. (I used 1066).

I hope this helps!

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://smackaho.st/|1|http://smackaho.st:54878/twitter/callback|blocks|key|1931305|text|使用http://smackaho.st|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|1931306|它所做的是一个到127.0.0.1的简单DNS关联，允许您绕过localhost或127.0.0.1上的过滤器：|1931308|+smackaho.st.28800英寸127.0.0.1|blockquote|1931311|因此，如果你点击这个链接，它会显示你在本地get服务器上有什么(如果你没有，你会得到一个404)。当然，您可以将其设置为您想要的任何页面/端口：|1931312|1931313^0|2|I|0|0|0|0|0|0|15|1|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]]|B|@$C|D|E|F|2|G|H|V|I|@]|J|@$K|W|L|X|C|Y]]|6|$]]|$C|M|E|N|2|G|H|Z|I|@]|J|@]|6|$]]|$C|O|E|P|2|Q|H|10|I|@]|J|@]|6|$]]|$C|R|E|S|2|G|H|11|I|@]|J|@]|6|$]]|$C|T|E|A|2|G|H|12|I|@]|J|@$K|13|L|14|C|15]]|6|$]]|$C|U|E|-4|2|G|H|16|I|@]|J|@]|6|$]]]]

Use <a href="http://smackaho.st" rel="noreferrer">http://smackaho.st</a>

What it does is a simple DNS association to 127.0.0.1 which allows you to bypass the filters on localhost or 127.0.0.1 : 

<blockquote>
 smackaho.st. 28800 IN A 127.0.0.1
</blockquote>

So if you click on the link, it will display you what you have on your local webserver (and if you don't have one, you'll get a 404). You can of course set it to any page/port you want : 

<a href="http://smackaho.st:54878/twitter/callback" rel="noreferrer">http://smackaho.st:54878/twitter/callback</a>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://twitter.local/|blocks|key|1931441|text|我在本地主机上使用Twitter回调url。如果您不确定如何创建虚拟主机(这一点很重要)，请使用Ampps。他真的很酷，也很随和。只需几个步骤，你就有了自己的虚拟主机，然后每个url都会在它上面工作。例如：|unstyled|depth|inlineStyleRanges|entityRanges|1931443|下载并安装ampps|ordered-list-item|1931444|添加新域。(您可以在此处设置例如twitter.local)，这意味着您的虚拟主机将是http://twitter.local，它将在步骤3之后工作。|offset|length|1931445|我正在处理Win，因此转到您的主机文件->+C:\Windows\System32\Drivers\etc\hosts并添加行:+127.0.0.1+twitter.local|1931447|重新启动放大器，然后就可以使用回调了。您可以指定任何url，即使您正在使用某个框架MVC或您有htaccess+url重写。|1931448|希望这对你有所帮助！干杯。|1931449^0|0|0|17|K|0|0|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|W|G|@]|H|@]|6|$]]|$A|I|C|J|2|K|F|X|G|@]|H|@]|6|$]]|$A|L|C|M|2|K|F|Y|G|@]|H|@$N|Z|O|10|A|11]]|6|$]]|$A|P|C|Q|2|K|F|12|G|@]|H|@]|6|$]]|$A|R|C|S|2|E|F|13|G|@]|H|@]|6|$]]|$A|T|C|U|2|E|F|14|G|@]|H|@]|6|$]]|$A|V|C|-4|2|E|F|15|G|@]|H|@]|6|$]]]]

I was working with Twitter callback url on my localhost. If you are not sure how to create a virtual host ( this is important ) use Ampps. He is really cool and easy. In a few steps you have your own virtual host and then every url will work on it. For example:

<ol>
<li>download and install ampps</li>
<li>Add new domain. ( here you can set for example twitter.local) that means your virtual host will be <a href="http://twitter.local" rel="noreferrer">http://twitter.local</a> and it will work after step 3.</li>
<li>I am working on Win so go under to your host file -> C:\Windows\System32\Drivers\etc\hosts and add line: 127.0.0.1 twitter.local</li>
</ol>

Restart your Ampps and you can use your callback. You can specify any url, even if you are using some framework MVC or you have htaccess url rewrite. 

Hope This Help!
Cheers.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://example.dev/|1|https://dev.twitter.com/discussions/5749|blocks|key|4041870|text|当我在本地开发时，我总是设置一个本地托管的开发人员名称，以反映我正在处理的项目。我在xampp中通过xampp\apache\conf\extra\httpd-vhosts.conf和\Windows\System32\drivers\etc\hosts设置了它。|unstyled|depth|inlineStyleRanges|entityRanges|4041871|因此，如果我要为example.com设置一个本地开发站点，我会在这两个文件中将其设置为example.dev。|4041872|简短回答：一旦设置正确，您就可以在设置Twitter应用程序时简单地将此url+(http://example.dev)视为活动的(而不是本地的)。|offset|length|style|BOLD|4041873|这里给出了一个类似的答案：https://dev.twitter.com/discussions/5749|4041874|直接报价(已强调)：|4041876|您可以使用我们在申请详情页上识别的域名提供任何有效的网址。OAuth+1.0a要求您在流的请求令牌步骤中发送一个LocaHost值，我们将在该步骤中接受一个基于动态oauth_callback的回调。|blockquote|4041879|这对我来说就像是一个护身符。希望这能有所帮助。|4041880^0|0|0|0|5|15|I|0|0|D|14|1|0|0|28|J|0|0^^$0|$1|$2|3|4|5|6|$7|8]]|9|$2|3|4|5|6|$7|A]]]|B|@$C|D|E|F|2|G|H|12|I|@]|J|@]|6|$]]|$C|K|E|L|2|G|H|13|I|@]|J|@]|6|$]]|$C|M|E|N|2|G|H|14|I|@$O|15|P|16|Q|R]]|J|@$O|17|P|18|C|19]]|6|$]]|$C|S|E|T|2|G|H|1A|I|@]|J|@$O|1B|P|1C|C|1D]]|6|$]]|$C|U|E|V|2|G|H|1E|I|@]|J|@]|6|$]]|$C|W|E|X|2|Y|H|1F|I|@$O|1G|P|1H|Q|R]]|J|@]|6|$]]|$C|Z|E|10|2|G|H|1I|I|@]|J|@]|6|$]]|$C|11|E|-4|2|G|H|1J|I|@]|J|@]|6|$]]]]

When I develop locally, I always set up a locally hosted dev name that reflects the project I'm working on. I set this up in xampp through xampp\apache\conf\extra\httpd-vhosts.conf and then also in \Windows\System32\drivers\etc\hosts.

So if I am setting up a local dev site for example.com, I would set it up as example.dev in those two files.

Short Answer: Once this is set up properly, you can simply treat this url (<a href="http://example.dev" rel="nofollow">http://example.dev</a>) as if it were live (rather than local) as you set up your Twitter Application.

A similar answer was given here: <a href="https://dev.twitter.com/discussions/5749" rel="nofollow">https://dev.twitter.com/discussions/5749</a>

Direct Quote (emphasis added): 

<blockquote>
 You can provide any valid URL with a domain name we recognize on the
 application details page. OAuth 1.0a requires you to send a
 oauth_callback value on the request token step of the flow and we'll
 accept a dynamic locahost-based callback on that step.
</blockquote>

This worked like a charm for me. Hope this helps.

entityMap|blocks|key|4041891|text|在#180行的TwitterAPIExchange.php上编辑此函数|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|4041892|public+function+performRequest($return+=+true)
{
++++if+(!is_bool($return))+
++++{+
++++++++throw+new+Exception('performRequest+parameter+must+be+true+or+false');+
++++}

++++$header+=+array($this->buildAuthorizationHeader($this->oauth),+'Expect:');

++++$getfield+=+$this->getGetfield();
++++$postfields+=+$this->getPostfields();

++++$options+=+array(+
++++++++CURLOPT_HTTPHEADER+=>+$header,
++++++++CURLOPT_HEADER+=>+false,
++++++++CURLOPT_URL+=>+$this->url,
++++++++CURLOPT_RETURNTRANSFER+=>+true,
++++++++CURLOPT_SSL_VERIFYPEER+=>+false,
++++++++CURLOPT_SSL_VERIFYHOST+=>+false
++++);

++++if+(!is_null($postfields))
++++{
++++++++$options[CURLOPT_POSTFIELDS]+=+$postfields;
++++}
++++else
++++{
++++++++if+($getfield+!==+'')
++++++++{
++++++++++++$options[CURLOPT_URL]+.=+$getfield;
++++++++}
++++}

++++$feed+=+curl_init();
++++curl_setopt_array($feed,+$options);
++++$json+=+curl_exec($feed);
++++curl_close($feed);

++++if+($return)+{+return+$json;+}
}|code-block|syntax|javascript|4041893^0|1|4|7|M|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|M|9|@$A|N|B|O|C|D]|$A|P|B|Q|C|D]]|E|@]|F|$]]|$2|G|4|H|6|I|8|R|9|@]|E|@]|F|$J|K]]|$2|L|4|-4|6|7|8|S|9|@]|E|@]|F|$]]]]

edit this function on TwitterAPIExchange.php at line #180

<pre><code>public function performRequest($return = true)
{
 if (!is_bool($return)) 
 { 
 throw new Exception('performRequest parameter must be true or false'); 
 }

 $header = array($this-&gt;buildAuthorizationHeader($this-&gt;oauth), 'Expect:');

 $getfield = $this-&gt;getGetfield();
 $postfields = $this-&gt;getPostfields();

 $options = array( 
 CURLOPT_HTTPHEADER =&gt; $header,
 CURLOPT_HEADER =&gt; false,
 CURLOPT_URL =&gt; $this-&gt;url,
 CURLOPT_RETURNTRANSFER =&gt; true,
 CURLOPT_SSL_VERIFYPEER =&gt; false,
 CURLOPT_SSL_VERIFYHOST =&gt; false
 );

 if (!is_null($postfields))
 {
 $options[CURLOPT_POSTFIELDS] = $postfields;
 }
 else
 {
 if ($getfield !== '')
 {
 $options[CURLOPT_URL] .= $getfield;
 }
 }

 $feed = curl_init();
 curl_setopt_array($feed, $options);
 $json = curl_exec($feed);
 curl_close($feed);

 if ($return) { return $json; }
}
</code></pre>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://tolocalhost.com/|blocks|key|1931675|text|我也遇到过同样的挑战，我无法将localhost作为有效的回调URL。所以我创建了一个简单的域来帮助我们开发人员：https://tolocalhost.com|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|1931676|它会将任何路径重定向到您需要的本地主机域和端口。希望能对其他开发者有所帮助。|1931677^0|1L|N|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|N|G|@]|H|@$I|O|J|P|A|Q]]|6|$]]|$A|K|C|L|2|E|F|R|G|@]|H|@]|6|$]]|$A|M|C|-4|2|E|F|S|G|@]|H|@]|6|$]]]]

I had the same challenge and I was not able to give localhost as a valid callback URL. So I created a simple domain to help us developers out:
<a href="https://tolocalhost.com" rel="nofollow noreferrer">https://tolocalhost.com</a>

It will redirect any path to your localhost domain and port you need. Hope it can be of use to other developers.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://readme.localtest.me/|blocks|key|5460534|text|似乎现在http://127.0.0.1也停止工作了。一个简单的解决方案是使用http://localtest.me而不是http://localhost，它总是指向127.0.0.1，您甚至可以向它添加任何子域，它仍然指向127.0.0.1|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|5460535|请参阅Website|5460536^0|4|G|13|J|1P|G|2B|9|34|9|0|3|7|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|P|G|@$H|Q|I|R|J|K]|$H|S|I|T|J|K]|$H|U|I|V|J|K]|$H|W|I|X|J|K]|$H|Y|I|Z|J|K]]|L|@]|6|$]]|$A|M|C|N|2|E|F|10|G|@]|L|@$H|11|I|12|A|13]]|6|$]]|$A|O|C|-4|2|E|F|14|G|@]|L|@]|6|$]]]]

Seems nowadays <code>http://127.0.0.1</code> also stopped working.
A simple solution is to use <code>http://localtest.me</code> instead of <code>http://localhost</code> it is always pointing to <code>127.0.0.1</code> And you can even add any arbitrary subdomain to it, and it will still point to <code>127.0.0.1</code>

See <a href="http://readme.localtest.me/" rel="nofollow noreferrer">Website</a>

entityMap|blocks|key|4041832|text|在twitter+app中设置callbackurl+:+127.0.0.1:3000，并将WEBrick设置为绑定到127.0.0.1而不是0.0.0.0|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4041833|命令:+rails+s+-b+127.0.0.1|4041834^0|0|0^^$0|$]|1|@$2|3|4|5|6|7|8|F|9|@]|A|@]|B|$]]|$2|C|4|D|6|7|8|G|9|@]|A|@]|B|$]]|$2|E|4|-4|6|7|8|H|9|@]|A|@]|B|$]]]]

set callbackurl in twitter app : 127.0.0.1:3000
and set WEBrick to bind on 127.0.0.1 instead of 0.0.0.0 

command : rails s -b 127.0.0.1

entityMap|blocks|key|1586991|text|看起来推特现在允许localhost和你在Callback+URL设置中的任何东西放在一起，只要那里有一个值。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1586992^0|9|9|L|C|0^^$0|$]|1|@$2|3|4|5|6|7|8|H|9|@$A|I|B|J|C|D]|$A|K|B|L|C|D]]|E|@]|F|$]]|$2|G|4|-4|6|7|8|M|9|@]|E|@]|F|$]]]]

Looks like Twitter now allows <code>localhost</code> alongside whatever you have in the <code>Callback URL</code> settings, so long as there is a value there.

entityMap|0|type|LINK|mutability|MUTABLE|data|url|https://codeload.github.com/VersatilityWerks/5719158/zip/master|blocks|key|4042053|text|我为此而苦苦挣扎，并遵循了十几种解决方案，最终，我要在本地主机上使用任何ssl+apis所需做的全部工作就是：|unstyled|depth|inlineStyleRanges|entityRanges|4042054|Go下载：cacert.pem+file|offset|length|4042055|在+php.ini+*+取消注释并更改：+curl.cainfo+=+"c:/wamp/bin/php/php5.5.12/cacert.pem"|style|CODE|ce8t4|您可以通过在+CLI+中运行+php+--ini+来找到您的+php.ini+文件在您的机器上的位置|unordered-list-item|475og|为方便起见，我将+cacert.pem+放在与+php.ini+相同的目录中。|4042059|4042060^0|0|5|F|0|0|2|7|L|1G|0|F|9|V|7|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|X|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|Y|G|@]|H|@$K|Z|L|10|A|11]]|6|$]]|$A|M|C|N|2|E|F|12|G|@$K|13|L|14|O|P]|$K|15|L|16|O|P]]|H|@]|6|$]]|$A|Q|C|R|2|S|F|17|G|@$K|18|L|19|O|P]|$K|1A|L|1B|O|P]]|H|@]|6|$]]|$A|T|C|U|2|S|F|1C|G|@]|H|@]|6|$]]|$A|V|C|-4|2|E|F|1D|G|@]|H|@]|6|$]]|$A|W|C|-4|2|E|F|1E|G|@]|H|@]|6|$]]]]

I struggled with this and followed a dozen solutions, in the end all I had to do to work with any ssl apis on local host was:

Go download: <a href="https://codeload.github.com/VersatilityWerks/5719158/zip/master" rel="nofollow">cacert.pem file</a>

In <code>php.ini</code> * un-comment and change: 
<code>
curl.cainfo = "c:/wamp/bin/php/php5.5.12/cacert.pem"
</code>

<ul>
<li>You can find where your <code>php.ini</code> file is on your machine by running <code>php --ini</code> in your CLI</li>
<li>I placed my cacert.pem in the same directory as php.ini for ease.</li>
</ul>

entityMap|0|type|LINK|mutability|MUTABLE|data|url|http://127.0.0.1/login/twitter/callback|blocks|key|1587090|text|以下是让Facebook在我的笔记本电脑上使用本地应用程序的工作步骤：|unstyled|depth|inlineStyleRanges|entityRanges|1587091|goto+apps.twitter.com|1587092|转到apps.twitter.com|unordered-list-item|e6sut|输入名称、应用程序描述和您的站点+URL+注意：对于+localhost:8000，请使用+127.0.0.1:8000，因为前者不起作用|av84d|输入与您的应用程序+TWITTER_REDIRECT_URI+中定义的回调+URL+匹配的回调+URL+注意：例如：http://127.0.0.1/login/twitter/callback（localhost+将不起作用）。|offset|length|5p8hg|如果您希望请求用户的电子邮件地址，请务必输入“隐私政策”和“使用条款”网址|3n3ba|选中同意条款复选框|8aih3|单击+[创建您的+Twitter+应用程序]|a69ee|切换到顶部的+[Keys+and+Access+Tokens]+选项卡|6qpqu|将“Consumer+Key（API+Key）”和“Consumer+Secret（API+Secret）”复制到您的应用程序中的TWITTER_KEY和TWITTER_SECRET|2g01|单击“权限”选项卡并适当设置为“只读”、“读写”或“读、写和直接消息”（使用您的应用程序所需的侵入性最小的选项，因为+OAuth+登录“只读”是充足的|f9odp|如果您希望将用户的电子邮件地址返回到+OAuth+登录数据，请在“其他权限”下选中“向用户请求电子邮件地址”复选框（在大多数情况下，请选中“是”）|1587102|1587103^0|0|0|0|0|1M|13|0|0|0|0|0|0|0|0|0|0^^$0|$1|$2|3|4|5|6|$7|8]]]|9|@$A|B|C|D|2|E|F|19|G|@]|H|@]|6|$]]|$A|I|C|J|2|E|F|1A|G|@]|H|@]|6|$]]|$A|K|C|L|2|M|F|1B|G|@]|H|@]|6|$]]|$A|N|C|O|2|M|F|1C|G|@]|H|@]|6|$]]|$A|P|C|Q|2|M|F|1D|G|@]|H|@$R|1E|S|1F|A|1G]]|6|$]]|$A|T|C|U|2|M|F|1H|G|@]|H|@]|6|$]]|$A|V|C|W|2|M|F|1I|G|@]|H|@]|6|$]]|$A|X|C|Y|2|M|F|1J|G|@]|H|@]|6|$]]|$A|Z|C|10|2|M|F|1K|G|@]|H|@]|6|$]]|$A|11|C|12|2|M|F|1L|G|@]|H|@]|6|$]]|$A|13|C|14|2|M|F|1M|G|@]|H|@]|6|$]]|$A|15|C|16|2|M|F|1N|G|@]|H|@]|6|$]]|$A|17|C|-4|2|E|F|1O|G|@]|H|@]|6|$]]|$A|18|C|-4|2|E|F|1P|G|@]|H|@]|6|$]]]]

These are the steps that worked for me to get Facebook working with a local application on my laptop:

<ul>
<li>goto apps.twitter.com</li>
<li>enter the name, app description and your site URL 
Note: for localhost:8000, use 127.0.0.1:8000 since the former will not work</li>
<li>enter the callback URL matching your callback URL defined in TWITTER_REDIRECT_URI your application
Note: eg: <a href="http://127.0.0.1/login/twitter/callback" rel="nofollow noreferrer">http://127.0.0.1/login/twitter/callback</a> (localhost will not work).</li>
<li>Important enter both the "privacy policy" and "terms of use" URLs if you wish to request the user's email address</li>
<li>check the agree to terms checkbox</li>
<li>click [Create Your Twitter Application]</li>
<li>switch to the [Keys and Access Tokens] tab at the top</li>
<li>copy the "Consumer Key (API Key)" and "Consumer Secret (API Secret)" to TWITTER_KEY and TWITTER_SECRET in your application</li>
<li>click the "Permissions" tab and set appropriately to "read only", "read and write" or "read, write and direct message" (use the least intrusive option needed for your application, for just and OAuth login "read only" is sufficient</li>
<li>Under "Additional Permissions" check the "request email addresses from users" checkbox if you wish for the user's email address to be returned to the OAuth login data (in most cases check yes)</li>
</ul>

Is anyone else having a difficult time getting Twitters oAuth's callback URL to hit their localhost development environment.
Apparently it has been disabled recently. <a href="http://code.google.com/p/twitter-api/issues/detail?id=534#c1" rel="noreferrer">http://code.google.com/p/twitter-api/issues/detail?id=534#c1</a>

Does anyone have a workaround. I don't really want to stop my development

Twitter oAuth callbackUrl - localhost development

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

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

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

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

社区新版编辑器体验调研

有没有其他人很难让Twitters oAuth的回调URL访问他们的本地主机开发环境。显然，它最近被禁用了。有没有人有办法。我真的不想停止我的发展

问Twitter oAuth callbackUrl -本地主机开发
EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Twitter oAuth callbackUrl -本地主机开发EN

回答 16

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Twitter oAuth callbackUrl -本地主机开发
EN