Loading Profile...
Why does my proxy complain about invalid requests from tracker ?
It seems that the WAKOOPA tracker only succeeds to upload data to the server on the first request.
From the second request on, the proxy is complaining about invalid http request, and no data arrives on the server.
I can provide a transcript of data written to consol by the tracker.
Running on Linux OpenSuse 11.1, using Squid as a proxy.
From the second request on, the proxy is complaining about invalid http request, and no data arrives on the server.
I can provide a transcript of data written to consol by the tracker.
Running on Linux OpenSuse 11.1, using Squid as a proxy.
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi!
A transcript would indeed be useful, can you paste it here? And is it possible for you to extract the exact reply of the Wakoopa servers from Squid?
Thanks!1 Comment
Add a comment
This answers the question
-
Hello Marten, I put the transcripts on the site for you. Were you able to look at it ? -
Inappropriate?Below the full transcript of wakoopa output when started in a terminal :
gillonr@gdv003:~> wakoopa
wakoopa: /usr/lib/libcurl.so.4: no version information available (required by wakoopa)
u:krugdvre
p:2148084aa3d3023cb40c54244abc7ba4e21eddf1
r:Wakoopa/1.1.1/linux
no_alerts:false
u=krugdvre&p=2148084aa3d3023cb40c54244abc7ba4e21eddf1&r=Wakoopa/1.1.1/linux&no_alerts=false
http://tracker.wakoopa.com/post/start
Using proxy:
127.0.0.1
<response>
<result>OK</result>
<time>1256153221</time>
<unread-alerts>0</unread-alerts>
<default-interval>900</default-interval>
<alerts type="array">
<alert>
<created-at type="datetime">2009-10-20T08:53:07Z</created-at>
<id type="integer">10829790</id>
<message>You reached a new level: novice</message>
<url>http://wakoopa.com/krugdvre</url>
<alert-type>
<id type="integer">14</id>
<name>user-level-up</name>
</alert-type>
<unread>false</unread>
</alert>
</alerts>
<new-version>false</new-version>
</response>
default-interval
900
unread-alerts
0
id
10829790
alert-type/id
14
unread
false
u:krugdvre
p:2148084aa3d3023cb40c54244abc7ba4e21eddf1
r:Wakoopa/1.1.1/linux
s:1256153216
o:SUSE LINUX/11.1 (openSUSE 11.1 (i586)) [32bit]
z:2
no_alerts:false
as:1256153217
h[]:1c7dc068efe028f97938d7de1ab74ea367f940da
t[]:[[0,0,3,0]]
h[]:1ef8a542ca25ddad2ce1548c83818d32d3505312
t[]:[[0,0,3,0]]
h[]:37c83db95c77e01ee27167371e5f2a66acd2d1b5
t[]:[[0,0,3,0]]
h[]:429a35c955539b89151019d520d1099cfcdd8029
t[]:[[0,0,3,0]]
h[]:46ce37bae20d732a18162ef791b1030d38ff6671
t[]:[[0,3,0,0]]
h[]:4cc2ad46dca02b49538667ebba8215526c75212b
t[]:[[0,0,3,0]]
h[]:80401adb1535d6273039d7aa67874720689ff06e
t[]:[[0,0,3,0]]
h[]:8884aef49df833ff16aa36b08f36df7c73de1319
t[]:[[0,0,3,0]]
h[]:8ebe439e5eb73ef30b18da21bc18e8d787986c79
t[]:[[0,0,3,0]]
h[]:9542354871341203a365534cc0aec0df18b40a4a
t[]:[[0,0,1,0]]
h[]:95cdfa82ed3e671906a53ab1249204c13827f1a0
t[]:[[0,0,3,0]]
h[]:cc1c3338c3aa5b1b6036daa85605e2733a0ecae8
t[]:[[0,0,3,0]]
h[]:e2a1c14c2593d8cda7be668560f2ea8ceb7ea05d
t[]:[[0,0,3,0]]
u=krugdvre&p=2148084aa3d3023cb40c54244abc7ba4e21eddf1&r=Wakoopa/1.1.1/linux&s=1256153216&o=SUSE+LINUX%2F11%2E1+%28openSUSE+11%2E1+%28i586%29%29+%5B32bit%5D&z=2&no_alerts=false&as=1256153217&h[]=1c7dc068efe028f97938d7de1ab74ea367f940da&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=1ef8a542ca25ddad2ce1548c83818d32d3505312&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=37c83db95c77e01ee27167371e5f2a66acd2d1b5&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=429a35c955539b89151019d520d1099cfcdd8029&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=46ce37bae20d732a18162ef791b1030d38ff6671&t[]=%5B%5B0%2C3%2C0%2C0%5D%5D&h[]=4cc2ad46dca02b49538667ebba8215526c75212b&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=80401adb1535d6273039d7aa67874720689ff06e&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=8884aef49df833ff16aa36b08f36df7c73de1319&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=8ebe439e5eb73ef30b18da21bc18e8d787986c79&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=9542354871341203a365534cc0aec0df18b40a4a&t[]=%5B%5B0%2C0%2C1%2C0%5D%5D&h[]=95cdfa82ed3e671906a53ab1249204c13827f1a0&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=cc1c3338c3aa5b1b6036daa85605e2733a0ecae8&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D&h[]=e2a1c14c2593d8cda7be668560f2ea8ceb7ea05d&t[]=%5B%5B0%2C0%2C3%2C0%5D%5D
http://tracker.wakoopa.com/post/batch
Using proxy:
127.0.0.1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html><head><meta />
<title>ERROR: The requested URL could not be retrieved</title>
<style type="text/css"><!--BODY{background-color:#ffffff;font-family:verdana,sans-serif}PRE{font-family:sans-serif}--></style>
</head><body>
<h1>ERROR</h1>
<h2>The requested URL could not be retrieved</h2>
<hr />
While trying to process the request:
POST /post/batch HTTP/1.1
Host: tracker.wakoopa.com
Pragma: no-cache
Accept: */*
Proxy-Connection: Keep-Alive
Content-Length: 1164
Content-Type: application/x-www-form-urlencoded
Expect: 100-continue
The following error was encountered:
Invalid Request
Some aspect of the HTTP Request is invalid. Possible problems:
- Missing or unknown request method
- Missing URL
- Missing HTTP Identifier (HTTP/1.0)
- Request is too large
- Content-Length missing for POST or PUT requests
- Illegal character in hostname; underscores are not allowed
Your cache administrator is webmaster.
<hr />
<address>
Generated Wed, 21 Oct 2009 19:27:01 GMT by gdv003.local (squid/2.7.STABLE5)
</address>
</body></html>
XML parser error:
expected =
Error while parsing XML data -
Inappropriate?Thanks for the detailed info and sorry for not responding earlier!
The problem is that Squid does not support the "Expect: 100-continue" part of the request to the Wakoopa server. We will remove it from the next tracker version which should make things work as expected!
Are you able to bypass the Squid proxy for the time being?
1 person says
this answers the question
-
Inappropriate?Marten,
OK, nice to hear you've identified the source of the problem.
On my side I found that all POST requests with a body shorter than 1016 were treated properly by Squid. Squid has some options to deal with 100-continue -- I will try it out (I tried many other settings like request_body_max_size options on squid but without success).
I will check if I can find a way to bypass squid for the moment.
Looking forward for the next tracker version -- when is it planned ?
I’m confident
-
Inappropriate?Marten,
I found a way to bypass squid by creating a wrapper script around wakoopa that removes all env variables defining the proxy and by creating a special rule with iptables in the NAT table on the PREROUTING chain that lets the tracker packets pass directly on port 80 (avoiding the REDIRECT put in place to enforce the proxy).
Now the tracker is connecting and reporting data properly.
I should also mention that I did not manage to find squid settings that work with the tracker -- bypass is the only solution at the moment.
I’m happy
-
Inappropriate?Hi Renaud,
Thanks for your investigation and info! We don't have a release date for the next version yet, but I will provide you with a temporary build so we can see if removing the Expect header fixes things for you. I will contact you in the next few days! -
Inappropriate?Hi Renaud,
We have a 1.1.1 version without the Expect: 100-continue header available. If you would like to test/use it you can contact us at info@wakoopa.com!
EMPLOYEE
