# URL Parameters priority

**URL:** <https://forum.inductiveautomation.com/t/url-parameters-priority/52598>\
**Category:** Ignition\
**Created:** [November 2, 2021, 1:07am UTC](https://forum.inductiveautomation.com/t/url-parameters-priority/52598 "2021-11-02T01:07:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael2](https://avatars.discourse-cdn.com/v4/letter/m/3e96dc/32.png) [@michael2](https://forum.inductiveautomation.com/u/michael2)\
**Post date:** [November 2, 2021, 1:07am UTC](https://forum.inductiveautomation.com/t/url-parameters-priority/52598/1 "2021-11-02T01:07:45Z")

</div>

Hi,

Just wondering how the URL parameters are supposed to work when you have pages that use the same prefix as a page with a URL parameter defined. For example, I have a page that is /page/:param, and some other pages such as /page/somePage defined, but only some of them are working as actual pages, while others are being treated as a param.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 2, 2021, 4:14pm UTC](https://forum.inductiveautomation.com/t/url-parameters-priority/52598/2 "2021-11-02T16:14:47Z")

</div>

I would expect that the more explicit page definition would ‘win’ over the passed parameter; if that’s not the behavior you’re seeing you may want to get in touch with support so they can investigate and potentially file a bug ticket.