Project

General

Profile

Actions

Bug #1068

closed

WMenu internal paths after refreshing page...

Added by Łukasz Matuszewski about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
11/22/2011
Due date:
% Done:

0%

Estimated time:

Description

When i try to refresh page after i click some menu item i get strange internal path.

Scenario:

1. Click on some menu item

Url will be: https://synat.eti.pg.gda.pl/wt/SyNaTPG.wt/menu_explorer?wtd=\[some_sess_data\]\[...\]

  1. Next when i refresh the page:
    Url will be: https://synat.eti.pg.gda.pl/wt/SyNaTPG.wt/menu_explorer/menu_expoler?wtd=\[some_sess_data\]\[...\]

I have attached the sample application, to show this. To see it in the real working system log to: https://synat.eti.pg.gda.pl/wt/SyNaTPG.wt with user: lukasz password: anakin and refresh the page.

BR

Łukasz Matuszewski


Files

SyNaTPG3.zip (36.4 KB) SyNaTPG3.zip Łukasz Matuszewski, 11/22/2011 02:28 PM
SyNaTPG3.zip (35.1 KB) SyNaTPG3.zip Łukasz Matuszewski, 11/22/2011 02:51 PM
Actions #1

Updated by Łukasz Matuszewski about 13 years ago

This is supposed to be in FastCGI, but i do not know if this is in WTHTTPD.

Actions #2

Updated by Łukasz Matuszewski about 13 years ago

Scenario:

1. Click on some menu item

Url will be: https://synat.eti.pg.gda.pl/wt/SyNaTPG.wt/menu_explorer?wtd=\[some_sess_data\]\[...\]

  1. Next when i refresh the page.
  2. Click on same menu item as in step 1.
    Url will be: https://synat.eti.pg.gda.pl/wt/SyNaTPG.wt/menu_explorer/menu_expoler?wtd=\[some_sess_data\]\[...\]

Re-uploading app... with script to build makefiles for fastcgi...

Actions #3

Updated by Koen Deforche about 13 years ago

  • Status changed from New to Feedback
  • Assignee set to Koen Deforche

Hey,

I couldn't reproduce your problem using the wthttpd and latest git. I used your build scripts and wt_config.xml file. What Wt version are you seeing the problem with, and did you also notice the problem using wthttpd ?

Regards,

koen

Actions #4

Updated by Łukasz Matuszewski about 13 years ago

I think this is only problem in fastcgi deployment.

Actions #5

Updated by Łukasz Matuszewski about 13 years ago

I am using version 3.1.11, and i think this also happens in wthttpd deployment. But if it is fixed in latest git then ok - so problem is soleved. I have used Firefox 8 to test it.

So i will be waiting for 3.2.0 :)

BR,

Lukasz Matuszewski

Actions #6

Updated by Koen Deforche about 13 years ago

  • Status changed from Feedback to Resolved
  • Target version set to 3.2.0

Hey Lukasz,

As I was reviewing changes since Wt 3.1.11, while preparing release notes for 3.2.0 I realize that this indeed (probably) has been fixed !

Regards,

koen

Actions #7

Updated by Koen Deforche about 13 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF