web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Pages - Customize & Extend
Suggested answer

Powerpager faulting when querystring exceeds 2048 bytes (?)

(0) ShareShare
ReportReport
Posted on by 1,214
Hi together,
we have a powerpage site with page which receives parameters via get and does something with them. This works up to the point, we place more than 2048 bytes in the querystring. The response from the portal is really a 404 and when i shorten the queryparameters, it works perfectly.
This is not an issue of the requesting browser. Chrome allows 2MB for requests and such a request also fails in postman for example.
As far as i know PowerPages is based on asp.net and i found this article: https://learn.microsoft.com/en-us/dotnet/api/system.web.configuration.httpruntimesection.maxquerystringlength?view=netframework-4.8.1 stating the default of 2048 characters.
This really smells like the problem. We are about to raise a ticket for that, but maybe there is someone out there who faced the same issue :-) .
 
Has anybody ancountered the same problems? Is there any sitesetting or something in any admincenter to raise that limit? Is that really the problem?
I could overcome this problem may be via using a post request, but then i would have to dig into the issue, how to read postparameters in liquid :-)
 
Many thanks for any hint on this,
  Christian
Categories:
I have the same question (0)
  • Suggested answer
    Fubar Profile Picture
    8,118 Super User 2025 Season 2 on at
    Powerpager faulting when querystring exceeds 2048 bytes (?)
    As far as I'm aware there isn't a Site Setting for it.
     
    Reading GET or POST in Liquid is pretty simple.
     
    But also maybe look at why you are sending so much data.
     
    Other options may include javascript to local storage, or if the data can be saved to dataverse (e.g. save using Portals Web API, on success redirect to the target page), then you can retrieve it on the target page using Liquid either using direct entity reference or fetchxml 
  • Suggested answer
    Shafiuddin Profile Picture
    74 on at
    Powerpager faulting when querystring exceeds 2048 bytes (?)
    Hi Christian, you’re right — the 2048-character cutoff comes from the underlying ASP.NET limit and Power Pages doesn’t let you change that with a site setting, so once your querystring exceeds that size you’ll always hit the 404; the usual workarounds are either switching to POST and handling the data server-side, or storing the parameters in Dataverse (or another store) and just passing a short token in the URL, which keeps things stable and avoids running into that built-in limit.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

MS.Ragavendar – Community Spotlight

We are honored to recognize Ragavendar Swaminatha Subramanian as our September…

Leaderboard > Power Pages

#1
Jon Unzueta Profile Picture

Jon Unzueta 89 Super User 2025 Season 2

#2
Shafiuddin Profile Picture

Shafiuddin 45

#3
Fubar Profile Picture

Fubar 40 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics