I can confirm this is the issue, had the exact same issue when writing
up some articles and this fixed it :)
On 03/29/2011 09:04 AM, Leif Hedstrom wrote:
On 03/29/2011 09:26 AM, Moshe Kaplan wrote:
Hi Leif,
Wired
1. I removed trailing slashes (I should not be the reason since it
worked
for
On 03/29/2011 11:10 AM, Moshe Kaplan wrote:
Thanks Leif, it worked!
One last thing, my brother (CC to this email) consider participating in the
Google Summer of Code (
http://www.google-melange.com/gsoc/homepage/google/gsoc2011).
Do you or any of the Traffic Server group consider to participate
Thanks Leif, it worked!
One last thing, my brother (CC to this email) consider participating in the
Google Summer of Code (
http://www.google-melange.com/gsoc/homepage/google/gsoc2011).
Do you or any of the Traffic Server group consider to participate as a
mentor in this program?
If so who should
On 03/29/2011 09:26 AM, Moshe Kaplan wrote:
Hi Leif,
Wired
1. I removed trailing slashes (I should not be the reason since it worked
for me on an incubator version)
Ahh, I think I know why, you have pristine host headers enabled (it's in
records.config). This makes the Host: header b
Hi Leif,
Wired
1. I removed trailing slashes (I should not be the reason since it worked
for me on an incubator version)
2. I compiled the 2.1.7 to verify, and I got the same behavior
3. Please find the results attached:
10x
Moshe
+ Incoming Request +
-- State Machin
On 03/29/2011 08:31 AM, Moshe Kaplan wrote:
Hi Leif,
10x for the quick answer
The remap.config is pretty simple (no plugins yet, just compiled the
code):
map http://ec2-50-17-143-39.compute-1.amazonaws.com/
http://www.google.com/
reverse_map http://www.google.com/
http://ec2-50-17-143-39.com
Hi Leif,
10x for the quick answer
The remap.config is pretty simple (no plugins yet, just compiled the code):
map http://ec2-50-17-143-39.compute-1.amazonaws.com/ http://www.google.com/
reverse_map http://www.google.com/
http://ec2-50-17-143-39.compute-1.amazonaws.com/
The server response using
On 03/29/2011 08:06 AM, Moshe Kaplan wrote:
Hi,
I installed the 2.1.8-unstable version on a new AWS image.
After configuring the remap.config (no plugin yet), I get following endless
loop of 301 to the same URL (Chrome provides the following message: The
webpage at http://ec2-50-17-143-39.comput
Hi,
I installed the 2.1.8-unstable version on a new AWS image.
After configuring the remap.config (no plugin yet), I get following endless
loop of 301 to the same URL (Chrome provides the following message: The
webpage at http://ec2-50-17-143-39.compute-1.amazonaws.com/ has resulted in
too many re
