Re: [E] Proposal for new TS plugin API function: TSUrlPortGet

In the first case it should return 0. In the second case it should return 61000. On Tue, Oct 6, 2020 at 4:02 PM Walt Karas wrote: > The current behavior that I'm seeing for TSUrlPortGet() is that for this > request: > > printf "GET / HTTP/1.1\r\nHost: mYhOsT.teSt:61000\r\n\r\n" | nc localhost >

Re: [E] Proposal for new TS plugin API function: TSUrlPortGet

The current behavior that I'm seeing for TSUrlPortGet() is that for this request: printf "GET / HTTP/1.1\r\nHost: mYhOsT.teSt:61000\r\n\r\n" | nc localhost 61001 it returns 80. Should TSUrlRawPortGet() return -1 ? For this request: printf "GET http://mYhOsT.teSt:61000/

Re: [E] Proposal for new TS plugin API function: TSUrlPortGet

After discussions, this will be changed to TSUrlRawPortGet that returns 0 if the port is not explicitly present in the URL. On Tue, Sep 29, 2020 at 9:28 AM Walt Karas wrote: > This gets the port string in the URL. If the port is not in the URL, it > returns nullptr (and sets length to zeor). Not

Proposal for new TS plugin API function: TSUrlPortGet

This gets the port string in the URL. If the port is not in the URL, it returns nullptr (and sets length to zeor). Note this is subtly different from TSUrlPortGet which always returns a valid port, the canonical port for the scheme if the port is not specified. Currently there is no way to detect t