On Thu, Jun 18, 2020 at 4:10 PM Risharde <risha...@gmail.com> wrote: > It seems that when the url is over 200+ characters, I get the issue >
Is there a missing zero there? The practical maximum URL length is around 2000, see also: https://stackoverflow.com/questions/29458445/what-is-a-safe-maximum-length-a-segment-in-a-url-path-should-be/33733386 https://www.abramillar.com/2018/02/12/urls-maximum-length-long-best/#:~:text=What%20Is%20the%20Maximum%20Length,able%20to%20load%20your%20page. Even a simple map preview URL generated by GeoServer goes beyond 200, I picked one at random for a single layer it was 240 chars. If you're hitting the 2000 chars limit, either find a way to make URLs shorter, or better yet, switch to a base library that is not limited to GET, such as OpenLayers. Another possible option would be to add a custom proxy in between, you give it "filters" and get back an identifier for each of them, then add just the id in the request, and as the request goes through the proxy, it will expand the full filter (since the hard limit is normally found in the browser, using a server side trick like this one would dodge it). Come to think of it, the GeoServer community module called "parameter extractor" does some of that, and has a REST API to create new mappings... but you'll have to access it with administrative credentials, which might be a significant limit for you. See: https://docs.geoserver.org/stable/en/user/community/params-extractor/index.html Cheers Andrea == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- *Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.*
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
