Author

Topic: Long Poll client - how to implement? (Read 1737 times)

legendary
Activity: 1596
Merit: 1012
Democracy is vulnerable to a 51% attack.
July 14, 2011, 09:00:30 AM
#4
You don't show the 'GET' line. But if it's anything other than "GET /LP HTTP/1.1", that's your problem.

For the reason the post above me explains -- see the "X-Long-Polling: /LP" header in the error reply.

By the way, you pasted your real Authorization. You better change the password for that worker before evil malicious bastards mine for you.



legendary
Activity: 2730
Merit: 1034
Needs more jiggawatts
July 14, 2011, 09:00:26 AM
#3
Are you sending it to the same URL as the regular getwork requests?

Look at the X-Long-Polling header in the responses to your regular getwork requests. They tell you where to send a long polling request, which may be a different URL.
sr. member
Activity: 324
Merit: 250
July 11, 2011, 09:57:55 PM
#2
need more info..

What miner you are using ?

Did u setup your own pool, or are you mining at btcguild ?
full member
Activity: 140
Merit: 100
July 10, 2011, 03:26:30 PM
#1
Hello,

simple problem. I work on a mining pool / proxy combo for my own use.

I now start dealing with long polling and id just will not work.

Why? Wink

I am submitting the same url I am getting and submitting work to, just as a GET instead of a POST, but I pretty much always get a 400 / Bad Request back.

I am having the following headers:

Content-Type: application/json-rpc
Authorization: Basic TmV0VGVjdHVyZV90dG86MjEyMzBhczIzOTg5MA==
Host: us.btcguild.com:8332

The non-LP part works fine, passwords etc. are all set.

What am I overlooking? Possibly something stupid, but I just can not figure out what Wink

Regards
Jump to: