Dear,

When upgrading to v15 (from v12) we caught some errors depending on code
in OWC where we tested for instance for "/something@".
Toggling between on and off for the compatibility database setting:
- Remove "/" on unknown URLs
removed some errors, but then some other errors were introduced.
I suspected that the definition of unknown URLs were changed over years so
I went to the documentation to understand what should be the standard
setting.
I became confused.

In docs for v12:

Do not remove “/” on unknown URLs: In former versions of 4D, unknown URLs
(URLs that do not correspond to an existing page nor to a 4D special URL)
were returned in the On Web Authentication and On Web Connection ($1)
database methods and did not begin with the “/” character. This specificity
was removed in 4D 2004. However, if you implemented algorithms based on this
special case and wish to keep the previous behavior, you can uncheck this
option.

In docs for v15R4:

Remove “/” on unknown URLs: In former versions of 4D, unknown URLs (URLs
that do not correspond to an existing page nor to a 4D special URL) were
returned in the On Web Authentication and On Web Connection ($1) database
methods and did not begin with the “/” character. This specificity was
removed in 4D 2004. However, if you implemented algorithms based on this
operation and wish to keep it, you can uncheck this option.


It seems that the standard should be to have this setting checked.
But does it mean that the / are removed or not?

Best Regards
Magnus Torell



--
View this message in context: 
http://4d.1045681.n5.nabble.com/Compatibility-Do-not-Remove-on-unknown-URLs-tp5747160.html
Sent from the 4D Tech mailing list archive at Nabble.com.
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to