Re: NNTP Bug in 2.72/2.73RC1 |
Mon, 03 October 2005 10:15 |
|
Did you provide the user name value and password inside the NNTP control panel for this import rule?
If you did, then please add debug code in nntp.php around the lines:
$nntp->user = $nntp_adm->login;
$nntp->pass = $nntp_adm->pass;
To see if the data is being retrieved properly
|
|
Re: NNTP Bug in 2.72/2.73RC1 |
Fri, 30 September 2005 20:47 |
|
Re #1
But rather than get an informative error message, they get a screen full of fputs/fgets attempting to write/read from an invalid stream resource.
Re #2
The authorization is working okay for a read from the nntp server, but a packet trace is showing no authorization info is being passed when posting - the "authinfo user" command is sent - but without the username, this results in a 501 error being returned from the nntp server. I don't know php particulary well, but don't see where the authorization info is being passed to the post routine.
H.
|
|
Re: NNTP Bug in 2.72/2.73RC1 |
Fri, 30 September 2005 14:44 |
|
Re #1
This is actually intentional behaviour the error message get written to a log but a script is not terminated. This is done so that when a user via the forum posts a message their response is not broken if syncronization to nntp fails.
Re #2
According to the code in CVS, which is the same as the one you see in 2.7.2 and 2.7.3RC1 the nntp code sents authetication via:
AUTHINFO user [actual_user_name]
|
|
NNTP Bug in 2.72/2.73RC1 |
Fri, 30 September 2005 12:12 |
|
New to FudForums, but really liking them. Found a problem with the released 2.72 and 2.73RC1 though. I'm mirroring an NNTP server into the forums. While trying to post any messages into the forums I was getting a stream of "invalid stream file errors". Finally traced it back to two things:
In nntp.inc
1) In the post function the return from Connect is set as $this->exit_handler(0) rather than $this->exit_handler() - this causes the actual nntp error to be hidden.
2) The underlying problem is that the post function doesn't receive the authorization credentials for the server. Looking at packet traces, during posting the nntp server is sent "authinfo user" rather than "authinfo user username", causing a 501 Invalid authorisation" error. Lacking the php knowledge to fix it properly, I've worked around it for now by hardcoding the username/password into the post function.
H.
|
|