Error 2252 with 23.7
 

I've been having trouble reporting results to primenet with several prime95 clients that were running version 23.7.1. I noticed another client running 23.4.1 was successfully connecting to primenet, and after back-leveling the 23.7 clients to 23.4, they also connect successfully.

Is anyone else seeing the same problem? A didn't see anything in a brief scan of the forum.

I traced the connect attempt of 23.4 and 23.7. 23.4 sends the following (good) HTTP request:

[CODE]GET [url]http://mersenne.org:80/cgi-bin/pnHttp.exe?ps&32516&.&.[/url] HTTP/1.0[/CODE]

while 23.7 is sending only:

[CODE]GET /cgi-bin/pnHttp.exe?ps&32516&.&. HTTP/1.0[/CODE]

with no Host: header in the request.

Any ideas on why 23.7 (also tried 23.8) sends the invalid HTTP request? Systems this is running on are both Win XP SP1 and W2K Pro & Server SP4.

Thanks,
Brian

Found the primenet.ini UseFullURL=1 setting in whatsnew.txt and that works for me with prime95 23.7. I never had problems communicating with primenet prior to 23.4 though (which the doc says always used relative urls?). It still looks like the current version of prime95 with no UseFullURL setting should be (but isn't) sending a Host: header in the request.

How did you trace it ?

I traced it with CommView, a Windows-based network/packet monitor, on the system I'm running Prime95 on. But I just tried it again and noticed something I hadn't noticed before -- when the request is sent, I don't receive any response whatsoever -- not even a TCP ack. That made me suspicious of my (external) firewall -- when I bypass the firewall, the short URL form now works OK.

And I must have been reading the HTTP 1.1 RFC previously also -- HTTP 1.1 requires the Host: header, but HTTP 1.0 doesn't. So since Prime95 claims to be sending an HTTP/1.0 request, it's not an invalid request as I originally thought.

Thanks for forcing me to look at this again. :redface:

OK you HTTP experts, you just volunteered to help fix prime95!

Prime95 (linux version) has always sent the relative URL. It was that way in the original code from Peter Hunter.
Windows Prime95 started using the same code in version 22.

To make some proxy servers happy, I tried sending full URLs. 99% of users were happy, but someone had a setup where that did not work.

So where do we go from here? Are there more than 3 choices:

1) Full URL.
2) Relative URL.
3) Relative URL with host:

Which should be the default? Should we try one and if we get an error (which errors?) try another?

What else should prime95 be doing?

Here is the relevant snippet from the HTTP1.1 spec.

[CODE]The Request-URI is a Uniform Resource Identifier (section 3.2) and
identifies the resource upon which to apply the request.

Request-URI = "*" | absoluteURI | abs_path | authority

The four options for Request-URI are dependent on the nature of the
request. The asterisk "*" means that the request does not apply to a
particular resource, but to the server itself, and is only allowed
when the method used does not necessarily apply to a resource. One
example would be

OPTIONS * HTTP/1.1

The absoluteURI form is REQUIRED when the request is being made to a
proxy. The proxy is requested to forward the request or service it
from a valid cache, and return the response.
[/CODE]

Option 3, relative URI with host field is the preferred method for contacting web servers but option 1 is REQUIRED for proxies.

[QUOTE=bej]
Any ideas on why 23.7 (also tried 23.8) ...

Thanks,
Brian[/QUOTE]

Version 23.8? I've never heard of it, and couldn't find it at [url]www.mersenne.org[/url].

[QUOTE=jinydu]Version 23.8? I've never heard of it, and couldn't find it at [url="http://www.mersenne.org"]www.mersenne.org[/url].[/QUOTE]
Try [url="ftp://mersenne.org/gimps/"]ftp://mersenne.org/gimps/[/url] . There you'll find statistics, new versions and stuff. E.g., [url="ftp://mersenne.org/gimps/p95v238.zip"]ftp://mersenne.org/gimps/p95v238.zip[/url]. :wink:

Cheers,

Benjamin