Comment by 🛸 bluesman
Re: "Lagrange and Scriptonite"
Thanks. This log helped me make sense of it. The first line is the redirect url created by the server. The second line is what the server gets from the client moments later. The third line is the "cleanup" redirect with the last being the result from the client. The issue is the handling of the "code" segment.
Alhena
Lagrange
So basically Lagrange isn't removing the '+' but it is removing the percent-encoding. (It's the server that removes the '+' when decoding. That's why it becomes %20 in the second redirect). The same happens with other chars encoded in redirect urls.
2025-07-31 · 9 months ago
1 Later Comment
🛸 bluesman [OP] · 2025-08-01 at 19:21:
It's not just redirects affected - or rather, erroneous redirects are a side effect. Give the following link:
Lagrange will interpret it as:
Even hovering the mouse over the link shows this alteration in the status bar.
Original Post
Lagrange and Scriptonite — After carrying on for weeks thinking Scriptonite was just fine and dandy, I find out a number of my sample scripts don't work in Lagrange. Long story short, my auto-prompt scheme relies on redirects. Right or wrong (someone tell me), Alhena redirects with the exact url sent in the status 30 message. It appears Lagrange will decode things in the url I intended to be preserved. Simple example: If my server builds a redirect url containing ";code=2%2B2", it becomes ";...