Diggbar modrewrite - 他们如何通过 modrewrite 传递 URL

Diggbar modrewrite- How do they pass URLs through modrewrite?(Diggbar modrewrite - 他们如何通过 modrewrite 传递 URL?)

问题描述

使用新的 Diggbar，您可以将 http://digg.com 放在您当前所在的任何 URL 前面，它会创建一个 Digg 短 URL.我只是假设他们通过 modrewrite 来做到这一点(尽管我不确定，因为我是新手).

With the new Diggbar, you can put http://digg.com in front of any URL that you are currently at and it will create a Digg short URL. I am only assuming they do this by modrewrite (though I am not sure since I am new at this all).

这是怎么做到的?在我看来，当我在我正在开发的网站上尝试此操作时，它会爆炸.

How is this done? It seems to me when I try this with a website I am working on, it bombs out.

我希望能够做到以下几点:

I want to be able to do the following:

http://example.com/http://stackoverflow.com/question/ask

并有一个 modrewrite 将允许这个去

and have a modrewrite that will allow this to go to

http://example.com/index.php?url=http://stackoverflow.com/question/ask

但是当我使用这个 modrewrite 时:

But when I use this modrewrite:

RewriteEngine on
RewriteRule ^([A-Za-z0-9]+)$ /message.php?id=$1 [L]

它不起作用.我做错了什么?

it doesn't work. What am I doing wrong?

推荐答案

您必须从 请求行 因为 Apache 删除了空路径段.最初请求的 URI 路径 /http://foobar/ 变为 /http:/foobar/.但请求行 (THE_REQUEST) 保持不变:

You have to take the value from the request line because Apache removes empty path segments. The initially requested URI path /http://foobar/ becomes /http:/foobar/. But the request line (THE_REQUEST) stays untouched:

RewriteCond %{THE_REQUEST} ^GET /(https?://[^s]+)
RewriteRule ^https?:/ index.php?url=%1 [L]

这篇关于Diggbar modrewrite - 他们如何通过 modrewrite 传递 URL?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！