🐞 反馈问题：前端页面组件的路由地址过长，会导致apisix网关返回502

[alex-ohhh]

请先确认以下事项：

• 请务必查看常见问题和故障排除
• 在 issues 页面搜索过问题（包括已关闭的 issue），但未能找到解决方法
• Rainbond 已升级到 最新版本

问题描述

Bug现象：前端项目集成keycloak后，如果路由地址过长或路由嵌套过深后刷新页面报错502如 图 1-1，主动切换该路由正常显示页面，只有在当前页刷新会502，在缩短的路由地址或嵌套路由地址，刷新均无此报错

该问题是否可以稳定重现？

可重现

重现步骤

前端组件写一个长的地址路由，然后请求该页面，进入后刷新，会触发

截图

日志

无

期望结果

正常返回请求的地址页面

解决方案（可选）

No response

操作系统 && Rainbond 版本

Ubuntu 20.04 Kubernetes版本: 1.30.4+rke2r1 Rainbond v6.6.0

是否愿意提交 PR 解决该问题？

• 我愿意提交 PR 来解决该问题

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Title: 🐞 Feedback problem: The routing address of the front-end page component is too long, which will cause the apisix gateway to return 502

[zzzhangqi]

我尝试了特别长的路由，发现确实会很慢，但能加载出来，你可以尝试给网关增加请求时长试试呢，默认是60s

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

I tried a particularly long route and found that it was indeed very slow, but it could be loaded. You can try increasing the request time for the gateway. The default is 60s.

[github-actions]

This issue has been marked as stale because it has been inactive.

It will be automatically closed in 1 day unless there is new activity.

If this is still relevant, please add a comment to keep it active.

Thank you for your contribution to the Rainbond project! 🙏