#1 No max-forwards header in the ACK after incoming 4xx

1.4.x
closed-invalid
modules (454)
3
2008-08-31
2008-08-07
Anonymous
No

Max-forwards must be added in the ACK sent by the SER after receiving 486 (as long as per other 4xx response coming from the User Agent Client).
SER is not adding it.

Tried to workaround with an
append_to_reply(txt)
or
append_hf(txt, hdr)
command but this header has not been added.

Discussion

  • Bogdan-Andrei Iancu

    Logged In: YES
    user_id=1275325
    Originator: NO

    The problem seams to be in TM module - when building local request, MF header is not populated.

    I will take a look into.

    Regards,
    Bogdan

     
  • Bogdan-Andrei Iancu

    • priority: 5 --> 7
    • assigned_to: nobody --> bogdan_iancu
    • labels: --> modules
    • milestone: --> 1.4.x
    • status: open --> open-accepted
     
  • Bogdan-Andrei Iancu

    Logged In: YES
    user_id=1275325
    Originator: NO

    Hi,

    After some investigation, it looks like TM does a proper job and adds NF header in all local generated ACKs and CANCELs..As all negative relies are local ACK-ed, the ACK for a 486 will contain the MF header.

    Please detail a bit the scenario where the MF is missing.

    Thanks and regards,
    Bogdan

     
  • Bogdan-Andrei Iancu

    • priority: 7 --> 3
    • status: open-accepted --> open-invalid
     
  • Bogdan-Andrei Iancu

    Logged In: YES
    user_id=1275325
    Originator: NO

    No feedback was received and the investigation results did not validate this report, so I will close it. If there are new arguments to sustain this report, please re-open it.

    Regards,
    Bodgdan

     
  • Bogdan-Andrei Iancu

    • status: open-invalid --> closed-invalid
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks