Question
Pegasystems Inc.
FR
Last activity: 22 Jan 2017 0:37 EST
How to solve "URI Too Large" when using URL obfuscation ?
Hello,
at my customer we are facing (when switching portals) a URI Too Large error returned by the firewall.
We are using URL obfuscation which seems to make the URI even longer.
The customer has been increasing the max length several times but we are now reaching a length of 3586 characters and they cannot increase more the URL length.
What is the recommended approach to follow in your option ?
Any way to make URLs shorter ?
Thanks in advance,
Pegasystems Inc.
IN
kindly review following post:
http://stackoverflow.com/questions/2891574/how-do-i-resolve-a-http-414-request-uri-too-long-error
Here, it talked for more than 8100 char.
Pegasystems Inc.
FR
Thank you for the pointer but the customer does not want to extend the length.
This is a public application, accessed from outside and they have pretty strict rules for their firewall.
What strategy can we use to reduce URL length ?
Pegasystems Inc.
IN
Hi Jeremy, Good morning!
- Sorry, I do not know...
- how to do/implement...
- but the component 'Pega Short URL Generator' publicised at https://pegaportal.pega.com/Pages/Home.aspx be of help?
- how to do/implement...
Please share your thoughts/comments, Thank you!
psahukaru
Pegasystems Inc.
IN
Pega product (PRPC) doesn't support short URL's as of now. Though there are discussions to implement shortURL and various presentations given to the product management , somehow product managers are not inclined to incorporate the stuff into product . Probable reason could be backward compatibility issues and the complex nature of dynamic url's constructed by pega javascript , DirectWebAccess and some other URL related features.
We did a POC last year and presented to the management but it never made into product for unknown reasons.
The URL shortener shown in pegaportal is for static purpose and will not serve the PRPC platform . May be you wanna raise an enhancment request with PEGA product .