|
HI All,
I have a customer who has a REST service deployed with IWS that is being
passed a URL parameter that contains a dash. The call works when no dashes
are in the parameters, but the service throws a 404 error right away when a
dash or other special character is found, even when the value is URL
encoded.
This call works. No dash.
http://1.1.1.1/web/services/SVC001/42192032701/
This fails with 404 error because of the dash
http://1.1.1.1/web/services/SVC001/42-192032701/
It looks like all parms are defined correctly in the IWS service and the
RPG seems fine.
Any thoughts on cause ?
Input appreciated.
Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.