You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had to implement a TFTP Client with RFC 1350 specifications for class and I think I found a bug where, when sending a file from client, the server expects first DATA block number to be 0 when it should be 1.
Here is what the documentation says: "The block numbers on data packets begin with one and increase by one for each new block of data."
Got into the code and printed the number the server receives and the one it expects. They are different so it stops the transfer.
Is this a bug or is it intentional and I'm missing something?
The text was updated successfully, but these errors were encountered:
I had to implement a TFTP Client with RFC 1350 specifications for class and I think I found a bug where, when sending a file from client, the server expects first DATA block number to be 0 when it should be 1.
Here is what the documentation says: "The block numbers on data packets begin with one and increase by one for each new block of data."
Got into the code and printed the number the server receives and the one it expects. They are different so it stops the transfer.
Is this a bug or is it intentional and I'm missing something?
The text was updated successfully, but these errors were encountered: