Bug #868: resolveRelativeUrl() seems to use outdated urls - Wt - Redmine

Actions

Copy link

Bug #868

closed

resolveRelativeUrl() seems to use outdated urls

Added by Boris Nagaev over 13 years ago. Updated over 13 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Target version:

3.1.10

Start date:

06/22/2011

Due date:

% Done:

Estimated time:

Description

I noticed a problem with new URL api:

Application is deployed at localhost:8000/
Open main page of application
Try to open other pages (under some internal path). There is WAnchor with internal path; new images are added in slot connected to wApp->internalPathChanged()
Images are loaded using relative path without "../"

I watched the value of pagePathInfo_ in WebSession::fixRelativeUrl() and it seems to be set to previous value of internal path, causing this error. When the nesting level of "folder" is changed, images can not be loaded.

Files

path.cpp (927 Bytes) path.cpp

Boris Nagaev, 06/27/2011 11:29 PM

Actions

Copy link

Updated by Koen Deforche over 13 years ago

Status changed from New to Resolved

Hey,

I fixed this (and some other problems) already in my private git copy.

Hopefully I can push my stash of work to the git repo tomorrow.

Regards,

koen

Actions

Copy link

Updated by Boris Nagaev over 13 years ago

File path.cpp path.cpp added

Hello,

I updated git, but it seems unfixed.

Look at file in attachment.

deploy command:

./path --docroot '.;/img' --http-address=0.0.0.0 --http-port=8003

This application should output (relative) path of image.

If http://localhost:8003/ is opened (ajax version), clicking at every anchor does not affect output (remains without "../", as path from root).

However, if application was started from for example http://localhost:8003/foo/, output is constantly "../img/1.img" (like from /foo/ rather than from real location).

The conclusion is that path in output seems to be one used when application was created.

Actions

Copy link