Project

General

Profile

Actions

Bug #1068

closed
ŁM KD

WMenu internal paths after refreshing page...

Bug #1068: WMenu internal paths after refreshing page...

Added by Łukasz Matuszewski almost 15 years ago. Updated almost 15 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\]\[...\]
2. 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

ŁM Updated by Łukasz Matuszewski almost 15 years ago Actions #1

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

ŁM Updated by Łukasz Matuszewski almost 15 years ago Actions #2

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\]\[...\]
2. Next when i refresh the page.
3. 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...

KD Updated by Koen Deforche almost 15 years ago Actions #3

  • 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

ŁM Updated by Łukasz Matuszewski almost 15 years ago Actions #4

I think this is only problem in fastcgi deployment.

ŁM Updated by Łukasz Matuszewski almost 15 years ago Actions #5

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

KD Updated by Koen Deforche almost 15 years ago Actions #6

  • 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

KD Updated by Koen Deforche almost 15 years ago Actions #7

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom