Replies: 5 comments 4 replies
-
(I should mention: I have other apps running just fine through narrowlink; FreshRSS is the first one I've had any troubles with.) |
Beta Was this translation helpful? Give feedback.
-
Hello, It is crucial for me to address the potential bugs on Narrowlink, so let's conduct an investigation. There is no manipulation or modification of cookies in Narrowlink, and they should transmit as they are. I have two hypotheses that might affect FreshRSS:
Please verify that the application works correctly on the local machine currently (using the original domain name for checking, you can edit the /etc/hosts file for this purpose). Also, verify that the Domain and Path attributes in the set-cookie response align with your configuration. If the above information doesn't help, you can compare the HTTP requests and responses that you see over Narrowlink with the ones you see in direct access. You can use developer options or tools like mitmproxy/burpsuite to access your communications. If you have any further questions or need assistance, please feel free to ask. P.S. I am rewriting the main components of Narrowlink to improve performance(using protobuf, multiplexing overwebsocket), scalability(horizontal), and simplicity(web panel) for the future #92. I'll also revisit this part to ensure everything works well. |
Beta Was this translation helpful? Give feedback.
-
Switching off http/2 in firefox allowed me to log in immediately! |
Beta Was this translation helpful? Give feedback.
-
I've just patched the issue #97 . You can refer to https://datatracker.ietf.org/doc/html/rfc9113#name-compressing-the-cookie-head to learn more about it. Thank you for reporting this issue. |
Beta Was this translation helpful? Give feedback.
-
I just rolled out version 0.2.4, which addressed this issue https://github.com/narrowlink/narrowlink/releases/tag/0.2.4 |
Beta Was this translation helpful? Give feedback.
-
Hi - I don't have enough information to make this a useful bug report, but I thought I'd ask for ideas. I'm trying to proxy the FreshRSS feed reader through a narrowlink web gateway, and it's telling me " The web server seems to be incorrectly configured for cookies required for PHP sessions!"
Digging around the FreshRSS github I didn't come up with a simple explanation of exactly what's missing, and honestly I'll be fine if it turns out I can't run FreshRSS through narrowlink just due to its PHP crankiness.
But I thought I'd ask in case there is some configuration in narrowlink I can tweak that will affect how its proxying affects cookies.
Beta Was this translation helpful? Give feedback.
All reactions