openresty / openresty/drizzle-nginx-module

How to change the return value

Open
#32 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
335
Forks
56
Avg merge
1h 31m
Merged PRs (30d)
2

Description

hello :

this is my conf

location /upload{
            root  /usr/local/software/appstorm;
           #rewrite ^upload/(.*)$ /usr/local/nginx/html/$1 last;
            #root /usr/local/nginx/html;
            index index.html index.htm;
     }


    location / {
        set $clientId $arg_clientId;
        set $id $arg_id;
        #set_quote_sql_str  $quoted_clientId $clientId;
        #set_quote_sql_str $quoted_id $id;
        #drizzle_query "select * from t_upgrade_user";
        drizzle_query "INSERT INTO t_upgrade_user(p_client_id,p_lib_id) values('$clientId','$id')";
        drizzle_pass mysqlbackend;
        drizzle_module_header off;
        #rds_json on;
        #root   /usr/local/software/appstorm;
        #root /usr/local/nginx/html;
        #index  index.html index.htm;
        rewrite ^/(.*)$ /upload/$1 last;
    }

Can be successfully inserted into the MySQL database, but as you can see I do not want to insert the successful state returned to client. I want to get the download path for root.

What can I do?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The relevant entry points are the posted nginx location /upload and location / blocks, especially drizzle_query, drizzle_pass, and rewrite. Read the module's documented behavior for these directives and trace the request flow first; done should be a documented, reproducible way to return the requested download path instead of the insert-success response.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, nginx
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.