Hi!

I think you've found the wrong mailing list for this post. This mailing
list is for discussing the development of Django itself, not for support
using Django. This means the discussions of bugs and features in Django
itself, rather than in your code using it. People on this list are unlikely
to answer your support query with their limited time and energy.

For support, please follow the "Getting Help" page:
https://docs.djangoproject.com/en/3.2/faq/help/ . This will help you find
people who are willing to support you, and to ask your question in a way
that makes it easy for them to answer.

Thanks for your understanding and all the best,

Adam

On Sun, 15 Aug 2021 at 11:06, Jack Dan <jekdani...@gmail.com> wrote:

> Hello everyone, please help me figure out the problem.
>
> This is a tricky question because I couldn't find anything on the net. I
> know how to encode / decode, I do not know where to do it. At what stage.
> The Django assembly is standard, it works fine on the local server, not on
> the hosting. The detailed situation is below.
>
> Hosting Support Conversation:
> *Me:* "On the local server everything works, but you don't. What is the
> reason?"
> *Support:*  "The web server cannot work with Cyrillic in links directly
> for work, it is converted accordingly. Therefore, when you open http: //
> dictionary.rf/pulpation, the web server converts pulpation to
> %25d0%25bf%25d1%2583%25d0%25bb%25d1%258c%25d0%25bf%25d0%25b0%25d1%2586%25d0%25b8%25d1%258f.
>
> Scripts of your site search in the database by the encoded value:
> SELECT `dictionary_d_word`.`id`, `dictionary_d_word`.`author_id`,
> `dictionary_d_word`.`word`, `dictionary_d_word`.`word_url`,
> `dictionary_d_word`.`description`, `dictionary_d_word`.`created_date`,
> `dictionary_d_word`.`published_date` FROM `dictionary_d_word` WHERE
> `dictionary_d_word`.`word_url` =
> '%25d0%25bf%25d1%2583%25d0%25bb%25d1%258c%25d0%25bf%25d0%25b0%25d1%2586%25d0%25b8%25d1%258f'
> LIMIT 21
>
> To avoid errors, you should decode the request value before executing the
> request, and then execute the request. "
>
> And I have a logical question:
> Where to decode this data?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/38d3588d-d4b7-4171-84c1-6cfb7387693bn%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/38d3588d-d4b7-4171-84c1-6cfb7387693bn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM35XCDQvuf9wfmV1nhaBtjWWcvym7V9633R-0oDzOc%3Dhw%40mail.gmail.com.
  • How... Jack Dan
    • ... 'Adam Johnson' via Django developers (Contributions to Django itself)

Reply via email to