How to handle internal paths when deploy-path ends with '/'?

Added by Стойчо Стефанов Stoycho Stefanov almost 13 years ago

Hi,

I compiled an application with both Wt-3.1.11 and Wt-3.2.1 and my deploy-path was an empty string:

server.addEntryPoint(Wt::Application, createApp, "", "/images/favicon.ico");

It looks like that Wt-3.2.1 sets one '&' too much before the session's id string at application start and than there are two '&'-s in the path when I click on the "home" menuItem of an WMenu with enabled internal paths:

wt3.2.1
    1. https://127.0.0.1/?&wtd=x9XM1Nj2Jj9iP5eG
    2. https://127.0.0.1/?_=/home&&wtd=x9XM1Nj2Jj9iP5eG

    [warning] "WApplication: Deploy-path ends with '/', using /?_= for internal paths"

wt3.1.11
    1. https://127.0.0.1/?wtd=AMmhYqYU8hh7bfJY&sid=1763400147
    3. https://127.0.0.1/?_=/home&wtd=Fz4ioLfSywWph1qf&sid=1163199893

    [warn] "Deploy-path ends with '/', using /?_= for internal paths"

All this results in an undesired behaviour of my application.

Is that a known problem and if so, is it fixed in the last release (3.2.2)?

Regards,

Stoycho

Replies (1)

RE: How to handle internal paths when deploy-path ends with '/'? - Added by Koen Deforche almost 13 years ago

Hey,

No, this isn't a known problem, and I'm fixing it now for the next release (candidate) for 3.2.2

Regards,

koen

(1-1/1)

Project

General

Profile

Wt