Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

On the Stack Exchange Data Explorer site, when I try to request a .CSV file for the query I've just made, I get the ASP.NET error "regurgitation" (I don't know that there's anything meaningful in the text, but I'll include it anyway):  

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

I get this in both Chrome and Firefox. I have tried it with 3 possible sites (SO, MSO, and SU) and 2 different queries.

share|improve this question
Did both queries have parameters? Looks like the URL isn't being updated properly in that case (which will result in an error). Looking into it now... – Tim Stone Jul 28 '12 at 13:54
@TimStone No additional parameters. I just ran… and… which only take UserID as a parameter. – jonsca Jul 28 '12 at 15:12
up vote 3 down vote accepted

Due to this change, we were stripping out the UserId parameter from the query string being passed to the link templates. This worked well for using the site-switching links, but less so for links that were referencing the results of what you just executed and needed the full set of parameters (like the CSV and query plan download ones).

I made sure those links get the parameters they need now and added a check in the CSV and query plan download routes to return a 400 Bad Request in the event that some of them are missing so we fail with something slightly more meaningful than the exception catch page.

The fix will hopefully go out in the near future, pending review. If you want, you can manually add the ?UserId=## to the end of the CSV download link in the meantime and it should be available for download.

share|improve this answer
Yes, the temporary fix worked. Thanks Tim! – jonsca Jul 28 '12 at 15:32

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .