Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8615647
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T05:25:50+00:00 2026-06-12T05:25:50+00:00

i am passing @Requestparam /register?name=newname from a page. but next time i call a

  • 0

i am passing @Requestparam /register?name=newname from a page. but next time i call a page /register/confirm, it’s showing the param in the url like /register/confirm?name=newname. how to avoid this?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T05:25:51+00:00Added an answer on June 12, 2026 at 5:25 am

    I recently had the same issue. This could happen because name is being confused with a Path in a @ModelAttribute. Do you have any such ModelAttribute in the same view ?

    I dont know how your view works, but it’s best that you refer to the @RequestParam as ${param.name} rather than name (in case you’re not already)

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

passing post data using cURL requires that the name of the input. However, I
When passing a date from datepicker to sort an excel table, somewhere the format
when passing parameters after index.php its showing 404 error .. its apache error not
warning: passing argument 1 of 'bsearch' makes pointer from integer without a cast and
When passing named parameters of the form :name to PDOStatement::bindParam() , it seems to
I'm passing to perl from php using escapeshellarg system(perl -e ' . escapeshellarg($inp) .
Passing messages around with actors is great. But I would like to have even
While passing data (Data Serialization) from Java (server) to Flex (client) the names of
I'm passing an object from client to server. Properties of the object which are
passing 0 as a limit argument prevents trailing empty strings, but how does one

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.