Discussions
Categories
- 196.9K All Categories
- 2.2K Data
- 239 Big Data Appliance
- 1.9K Data Science
- 450.4K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 546 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.9K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.6K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 155 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 18 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 442 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Parameters dropped from URL

I have some APEX applications that send emails to users. Some of these emails contain deep links back to the application.
Prior to upgrading to 4.2.3 these links worked properly.
After upgrading to 4.2.3 the links still work be the parameters are dropped.
For example, if the original link is: http://tec-apex04:7777/pls/apex/f?p=140:10:2903726337254566::NO::P10_ID:4269
The page in the browser will display: http://tec-apex04:7777/pls/apex/f?p=140:10:2903726337254566.
So the page displayed but no data has been fetched so all the fields are blank
I am pretty sure this has something to do with the session id. I can actually see the full URL being displayed for a second and then the truncated one shows up.
Note that the URL that is in the email has a random session id. Also, the session id that is displayed in the browser once the parameters are dropped is a new, different one.
If I leave the browser open and click on the email link a second time, the browser opens a new tab and the parameters are retained. At this point the second tab uses the session id created on the first try.
Like I said, this used to work fine before. Has something changed in the new version to prevent me from doing this?
Thanks for your help!